CVE-2025-22018: atm: Fix NULL pointer dereference
Published Apr 16, 2025
·Updated
atm: Fix NULL pointer dereference
Affected Software
11 affected componentsFixes available
Linux Kernel
Linux Linux kernel>=2.6.12<5.4.292
Linux Linux kernel>=5.5<5.10.236
Linux Linux kernel>=5.11<5.15.180
Linux Linux kernel>=5.16<6.1.133
Linux Linux kernel>=6.2<6.6.86
Linux Linux kernel>=6.7<6.12.22
Linux Linux kernel>=6.13<6.13.10
Linux Linux kernel>=6.14<6.14.1
Microsoft azl3 kernel 6.6.92.2-1
Microsoft azl3 kernel 6.6.85.1-4
Remediation
Event History
Apr 16, 2025
CVE Published
via MITRE·05:04 AM
Data Sourced
via MITRE·05:04 AM
Description
Data Sourced
via NVD·05:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 11, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-22018?
CVE-2025-22018 is classified as a null pointer dereference vulnerability in the Linux kernel.
2
How do I fix CVE-2025-22018?
To fix CVE-2025-22018, ensure that your Linux kernel is updated to the latest patched version addressing this vulnerability.
3
Which versions of the Linux kernel are affected by CVE-2025-22018?
CVE-2025-22018 affects multiple versions of the Linux kernel where the MPOA_cache_impos_rcvd() function improperly handles null pointers.
4
What are the consequences of CVE-2025-22018 if exploited?
If exploited, CVE-2025-22018 can lead to a system crash or potential denial of service due to null pointer dereference.
5
Who is responsible for fixing CVE-2025-22018?
The maintainers of the Linux kernel are responsible for fixing CVE-2025-22018 and releasing updates.