CVE-2025-38460: atm: clip: Fix potential null-ptr-deref in to_atmarpd().
Published Jul 25, 2025
·Updated
atm: clip: Fix potential null-ptr-deref in toatmarpd().
Affected Software
22 affected componentsFixes available
Microsoft azl3 kernel 6.6.96.2-1
Microsoft azl3 kernel 6.6.96.2-2
Microsoft cbl2 kernel 5.15.186.1-1
Linux Linux kernel>=2.6.13<5.4.296
Linux Linux kernel>=5.5<5.10.240
Linux Linux kernel>=5.11<5.15.189
Linux Linux kernel>=5.16<6.1.146
Linux Linux kernel>=6.2<6.6.99
Linux Linux kernel>=6.7<6.12.39
Linux Linux kernel>=6.13<6.15.7
Linux Linux kernel=2.6.12
Linux Linux kernel=2.6.12-rc2
Linux Linux kernel=2.6.12-rc3
Linux Linux kernel=2.6.12-rc4
Linux Linux kernel=2.6.12-rc5
Linux Linux kernel=6.16-rc1
Linux Linux kernel=6.16-rc2
Linux Linux kernel=6.16-rc3
Linux Linux kernel=6.16-rc4
Linux Linux kernel=6.16-rc5
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.
- Upgrade
Upgrade
debian/linuxto 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 25, 2025
CVE Published
via MITRE·03:27 PM
Data Sourced
via MITRE·03:27 PM
DescriptionSeverity
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 3, 2025
Data Sourced
via Microsoft·11:36 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-38460?
CVE-2025-38460 is classified as a serious vulnerability due to its potential for null pointer dereference.
2
How do I fix CVE-2025-38460?
To fix CVE-2025-38460, you should upgrade to the latest version of the Linux kernel that includes the patch for this vulnerability.
3
Which versions of Linux kernel are affected by CVE-2025-38460?
CVE-2025-38460 affects multiple versions of the Linux kernel from 2.6.12 to versions before 6.16.
4
Is CVE-2025-38460 a remote code execution vulnerability?
CVE-2025-38460 does not directly lead to remote code execution but could result in system instability.
5
When was CVE-2025-38460 discovered?
The discovery date for CVE-2025-38460 has not been publicly disclosed.