Local service interruption via unlocked multicast-table cleanup
Published Jul 16, 2024 · Updated May 11, 2026
Improper locking in the Linux kernel 4.0 through 5.16 allows local users to interrupt service during multicast-routing initialization. The ipmr and ip6mr initialization failure paths call ipmr_free_table or ip6mr_free_table without first acquiring the required RTNL lock. Reaching the failure path requires local low-privileged access; the unlocked cleanup triggers an unregister_netdevice_many assertion and disrupts availability.
Summary
What happened
Improper locking in the Linux kernel 4.0 through 5.16 allows local users to interrupt service during multicast-routing initialization. The ipmr and ip6mr initialization failure paths call ipmr_free_table or ip6mr_free_table without first acquiring the required RTNL lock. Reaching the failure path requires local low-privileged access; the unlocked cleanup triggers an unregister_netdevice_many assertion and disrupts availability.
The record
- CVE
- CVE-2022-48810
- Published
- Jul 16, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 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=4.0
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <09ac0fcb0a82d647f2c61d3d488d367b7ee5bd51
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <12b6703e9546902c56b4b9048b893ad49d62bdd4
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <16dcfde98a25340ff0f7879a16bea141d824a196
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <3cab045c99dbb9a94eb2d1d405f399916eec698a
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <5611a00697c8ecc5aad04392bea629e9d6a20463
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <80c529322600dfb1f985b5e3f14c3c6f522ce154
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <b541845dfc4e7df551955e70deec0921d6b297c3
- Affected versionversion=f243e5a7859a24d10975afb9a1708cac624ba6f1 <feb9597e22755dce782aae26ac0590c06737e049
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.
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