CVE-2025-38310: seg6: Fix validation of nexthop addresses

Published Jul 10, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

seg6: Fix validation of nexthop addresses

The kernel currently validates that the length of the provided nexthop address does not exceed the specified length. This can lead to the kernel reading uninitialized memory if user space provided a shorter length than the specified one.

Fix by validating that the provided length exactly matches the specified one.

Affected Software

8 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=4.14<5.15.186
Linux Linux kernel>=5.16<6.1.142
Linux Linux kernel>=6.2<6.6.94
Linux Linux kernel>=6.7<6.12.34
Linux Linux kernel>=6.13<6.15.3
Debian Debian Linux=11.0
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1

Event History

Jul 10, 2025
CVE Published
via MITRE·07:42 AM
Data Sourced
via MITRE·07:42 AM
Description
Data Sourced
via NVD·08:15 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2025-38310?

CVE-2025-38310 has a medium severity rating due to its potential impact on kernel memory access.

2

How do I fix CVE-2025-38310?

To address CVE-2025-38310, update the Linux kernel to a version where this vulnerability has been patched.

3

What systems are affected by CVE-2025-38310?

CVE-2025-38310 affects all versions of the Linux kernel that have not been updated to include the fix.

4

Can CVE-2025-38310 lead to exploitation?

Yes, CVE-2025-38310 can lead to exploitation by allowing unauthorized access to memory, which may compromise system stability.

5

Is there a workaround for CVE-2025-38310?

There are no known effective workarounds for CVE-2025-38310, so applying the official kernel update is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203