Kernel crash via null ROSE neighbor device
Published May 1, 2025 · Updated May 23, 2026
NULL pointer dereference in the Linux kernel ROSE subsystem allows local users to crash the kernel through a crafted ROSE socket sequence. rose_transmit_clear_request passes rose_loopback_neigh with a null dev member to rose_send_frame, which dereferences neigh->dev->dev_addr. The trigger requires local low-privileged access and ROSE protocol use; successful exploitation interrupts the operating system without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in the Linux kernel ROSE subsystem allows local users to crash the kernel through a crafted ROSE socket sequence. rose_transmit_clear_request passes rose_loopback_neigh with a null dev member to rose_send_frame, which dereferences neigh->dev->dev_addr. The trigger requires local low-privileged access and ROSE protocol use; successful exploitation interrupts the operating system without reported data disclosure or modification.
The record
- CVE
- CVE-2022-49916
- Published
- May 1, 2025
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 23, 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=0aae33feb7a56b28318f92c960a3d08d9c305984 <5b46adfbee1e429f33b10a88d6c00fa88f3d6c77
- Affected versionversion=3c53cd65dece47dd1f9d3a809f32e59d1d87b2b8 <a601e5eded33bb88b8a42743db8fef3ad41dd97e
- Affected versionversion=3c53cd65dece47dd1f9d3a809f32e59d1d87b2b8 <e97c089d7a49f67027395ddf70bf327eeac2611e
- Affected versionversion=4.14.292 <4.14.299
- Affected versionversion=4.19.257 <4.19.265
- Affected versionversion=4.9.327 <4.9.333
- Affected versionversion=5.10.140 <5.10.154
- Affected versionversion=5.15.64 <5.15.78
- Affected versionversion=5.19.6 <5.20
- Affected versionversion=5.4.212 <5.4.224
- Affected versionversion=6.0
- Affected versionversion=6e4b20d548fc97ecbdca15c8d96302ee5e3e6313 <b13be5e852b03f376058027e462fad4230240891
- Affected versionversion=76885373129b13df35ecc9b4ee86ea5840f12133 <01b9c68c121847d05a4ccef68244dadf82bfa331
- Affected versionversion=9197ca40fd9de265caedba70d0cb5814c4e45952
- Affected versionversion=9cf85759e104d7e9c3fd8920a554195b715d6797 <3e2129c67daca21043a26575108f6286c85e71f6
- Affected versionversion=b8f9de195d6303f52bae16c7911f35ac14ba7e3d <bbc03d74e641e824754443b908454ca9e203773e
- Affected versionversion=de3deadd11987070788b48825bec4647458b988d <f06186e5271b980bac03f5c97276ed0146ddc9b0
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
- syz reproducer for the ROSE null dereferenceproof of concept · demonstrated
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