Kernel panic via unavailable network driver data
Published Dec 27, 2024 · Updated May 11, 2026
A release-path flaw in the Linux User-Mode Linux network driver allows local users to crash the kernel by removing a network device. The net_device_release function obtains uml_net through dev_get_drvdata after driver data is unavailable, dereferencing an invalid pointer instead of deriving the containing object. The flaw is confined to a User-Mode Linux instance, requires low-privileged local access, and causes a kernel panic rather than data disclosure or modification.
Summary
What happened
A release-path flaw in the Linux User-Mode Linux network driver allows local users to crash the kernel by removing a network device. The net_device_release function obtains uml_net through dev_get_drvdata after driver data is unavailable, dereferencing an invalid pointer instead of deriving the containing object. The flaw is confined to a User-Mode Linux instance, requires low-privileged local access, and causes a kernel panic rather than data disclosure or modification.
The record
- CVE
- CVE-2024-53183
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.22
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <160cd5f956d191eb97664afd31ca59284c08d876
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <1635d9a0ff1b8bd7aa4767d4ea7b3de72cd36f28
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <468c2e5394afc848efb1eae6e1961a3c855cf35e
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <6be99d4c117b9642a44d9f54f034b67615be2b2b
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <8d9d174d3f55daaf5e7b48e9d7f53c723adbed86
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <b174ab33aaafd556a1ead72fa8e35d70b6fb1e39
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <cdbd5a1dcdc2c27ac076f91b03b9add3fefa1a82
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <d1db692a9be3b4bd3473b64fcae996afaffe8438
- Affected versionversion=2e3f5251ac716879df6b6271f243f657c6e02e9a <f04cd022ee1fde219e0db1086c27a0a5ba1914db
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo