Kernel crash via cleared TIPC socket dereference
Published Dec 27, 2024 · Updated May 11, 2026
NULL pointer dereference in Linux TIPC UDP bearer cleanup allows local users with low privileges to crash an affected kernel. The cleanup_bearer function reads ub->ubsock->sk after the socket pointer has become NULL and passes it through sock_net while decrementing wq_count. Reaching the faulty cleanup path requires local low-privileged access and a TIPC UDP bearer; the resulting kernel fault interrupts system availability.
Summary
What happened
NULL pointer dereference in Linux TIPC UDP bearer cleanup allows local users with low privileges to crash an affected kernel. The cleanup_bearer function reads ub->ubsock->sk after the socket pointer has become NULL and passes it through sock_net while decrementing wq_count. Reaching the faulty cleanup path requires local low-privileged access and a TIPC UDP bearer; the resulting kernel fault interrupts system availability.
The record
- CVE
- CVE-2024-56661
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- 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=4e69457f9dfae67435f3ccf29008768eae860415 <d1d4dfb189a115734bff81c411bc58d9e348db7d
- Affected versionversion=5.10.231 <5.10.232
- Affected versionversion=5.15.174 <5.15.175
- Affected versionversion=5.4.287 <5.4.288
- Affected versionversion=6.1.120 <6.1.121
- Affected versionversion=6.12.5 <6.12.6
- Affected versionversion=650ee9a22d7a2de8999fac2d45983597a0c22359 <a771f349c95d3397636861a0a6462d4a7a7ecb25
- Affected versionversion=6.6.66 <6.6.67
- Affected versionversion=6a2fa13312e51a621f652d522d7e2df7066330b6 <b04d86fff66b15c07505d226431f808c15b1703c
- Affected versionversion=d00d4470bf8c4282617a3a10e76b20a9c7e4cffa <89ecda492d0a37fd00aaffc4151f1f44c26d93ac
- Affected versionversion=d2a4894f238551eae178904e7f45af87577074fd <07b569eda6fe6a1e83be5a587abee12d1303f95e
- Affected versionversion=d62d5180c036eeac09f80660edc7a602b369125f <754ec823ee53422361da7958a8c8bf3275426912
- Affected versionversion=e48b211c4c59062cb6dd6c2c37c51a7cc235a464 <a852c82eda4991e21610837aaa160965be71f5cc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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