CVE-2025-39702: ipv6: sr: Fix MAC comparison to be constant-time
Published Sep 5, 2025
·Updated
In the Linux kernel, the following vulnerability has been resolved:
ipv6: sr: Fix MAC comparison to be constant-time
To prevent timing attacks, MACs need to be compared in constant time. Use the appropriate helper function for this.
Affected Software
12 affected componentsFixes available
Linux Kernel
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.96.2-1
Linux Linux kernel>=4.10<5.15.190
Linux Linux kernel>=5.16<6.1.149
Linux Linux kernel>=6.2<6.6.103
Linux Linux kernel>=6.7<6.12.44
Linux Linux kernel>=6.13<6.16.4
Linux Linux kernel=6.17-rc1
Linux Linux kernel=6.17-rc2
Debian Debian Linux=11.0
Microsoft cbl2 kernel 5.15.186.1-1
Event History
Sep 5, 2025
CVE Published
via MITRE·05:21 PM
Data Sourced
via MITRE·05:21 PM
DescriptionSeverity
Data Sourced
via Red Hat·06:04 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 7, 2025
Data Sourced
via Microsoft·01:03 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:03 AM
SeverityAffected Software
Updated
via Microsoft·08:03 AM
SeverityAffected Software
Updated
via Microsoft·08:03 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-39702?
CVE-2025-39702 has a moderate severity rating due to its potential for timing attacks.
2
How do I fix CVE-2025-39702?
To fix CVE-2025-39702, update your Linux kernel to the latest patched version that addresses this vulnerability.
3
What systems are affected by CVE-2025-39702?
CVE-2025-39702 affects all versions of the Linux kernel that are vulnerable to improper MAC comparisons.
4
Is CVE-2025-39702 a critical vulnerability?
No, CVE-2025-39702 is not classified as a critical vulnerability but should still be addressed promptly.
5
Can CVE-2025-39702 lead to data exposure?
Yes, CVE-2025-39702 could potentially expose sensitive data through timing attacks if not mitigated.