CVE-2024-53184: um: ubd: Do not use drvdata in release
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 16cf8511680809a9f20b3dd224c06d482648f9e2, 23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8, 2d194d951895df214e066d08146e77cb6e02c1d4.
Low priority for now. Upgrade to Linux Linux 16cf8511680809a9f20b3dd224c06d482648f9e2, 23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8, 2d194d951895df214e066d08146e77cb6e02c1d4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: um: ubd: Do not use drvdata in release The drvdata is not available in release. Let's just use container_of() to get the ubd instance. Otherwise, removing a ubd device will result in a crash: RIP: 0033:blk_mq_free_tag_set+0x1f/0xba RSP: 00000000e2083bf0 EFLAGS: 00010246 RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00 RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348 RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7 R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000 R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0 Kernel panic - not syncing: Segfault with no mm CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1 Workqueue: events mc_work_proc Stack: 00000000 604f7ef0 62c5d000 62405d20 e2083c30 6002c776 6002c755 600e47ff e2083c60 6025ffe3 04208060 603d36e0 Call Trace: [<6002c776>] ubd_device_release+0x21/0x55 [<6002c755>] ? ubd_device_release+0x0/0x55 [<600e47ff>] ? kfree+0x0/0x100 [<6025ffe3>] device_release+0x70/0xba [<60381d6a>] kobject_put+0xb5/0xe2 [<6026027b>] put_device+0x19/0x1c [<6026a036>] platform_device_put+0x26/0x29 [<6026ac5a>] platform_device_unregister+0x2c/0x2e [<6002c52e>] ubd_remove+0xb8/0xd6 [<6002bb74>] ? mconsole_reply+0x0/0x50 [<6002b926>] mconsole_remove+0x160/0x1cc [<6002bbbc>] ? mconsole_reply+0x48/0x50 [<6003379c>] ? um_set_signals+0x3b/0x43 [<60061c55>] ? update_min_vruntime+0x14/0x70 [<6006251f>] ? dequeue_task_fair+0x164/0x235 [<600620aa>] ? update_cfs_group+0x0/0x40 [<603a0e77>] ? __schedule+0x0/0x3ed [<60033761>] ? um_set_signals+0x0/0x43 [<6002af6a>] mc_work_proc+0x77/0x91 [<600520b4>] process_scheduled_works+0x1af/0x2c3 [<6004ede3>] ? assign_work+0x0/0x58 [<600527a1>] worker_thread+0x2f7/0x37a [<6004ee3b>] ? set_pf_worker+0x0/0x64 [<6005765d>] ? arch_local_irq_save+0x0/0x2d [<60058e07>] ? kthread_exit+0x0/0x3a [<600524aa>] ? worker_thread+0x0/0x37a [<60058f9f>] kthread+0x130/0x135 [<6002068e>] new_thread_handler+0x85/0xb6
- Published
- Dec 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 4.19.325
- linux linux kernel4.20 and later · before 5.4.287
- linux linux kernel5.5 and later · before 5.10.231
- linux linux kernel5.11 and later · before 5.15.174
- linux linux kernel5.16 and later · before 6.1.120
- linux linux kernel6.2 and later · before 6.6.64
- linux linux kernel6.7 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.6affected
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before 23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8affected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before 300e277e463e6326938dd55ea560eafa0f5c88a5affected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before 509ba8746f812e45a05034ba18b73db574693d11affected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before 5727343348f34e11a7c5a2a944d5aa505731d876affected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before a5a75207efae4b558aaa34c288de7d6f2e926b4baffected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before 2d194d951895df214e066d08146e77cb6e02c1d4affected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before e6e5a4cded9bef3a1b0a4fac815b7176eb9a18ecaffected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before 16cf8511680809a9f20b3dd224c06d482648f9e2affected · git
- 0998d0631001288a5974afc0b2a5f568bcdecb4d and later · before 5bee35e5389f450a7eea7318deb9073e9414d3b1affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-53182Dec 27, 2024 · Revert "block, bfq: merge bfq_release_process_ref() into bfq_put_cooperator()"31Monitor
- ← EarlierCVE-2024-53183Dec 27, 2024 · um: net: Do not use drvdata in release22Monitor
- Later →CVE-2024-53185Dec 27, 2024 · smb: client: fix NULL ptr deref in crypto_aead_setkey()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 16cf8511680809a9f20b3dd224c06d482648f9e2 | Vendor (CNA) |
| Linux Linux | 23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8 | Vendor (CNA) |
| Linux Linux | 2d194d951895df214e066d08146e77cb6e02c1d4 | Vendor (CNA) |
| Linux Linux | 300e277e463e6326938dd55ea560eafa0f5c88a5 | Vendor (CNA) |
| Linux Linux | 509ba8746f812e45a05034ba18b73db574693d11 | Vendor (CNA) |
| Linux Linux | 5727343348f34e11a7c5a2a944d5aa505731d876 | Vendor (CNA) |
| Linux Linux | 5bee35e5389f450a7eea7318deb9073e9414d3b1 | Vendor (CNA) |
| Linux Linux | a5a75207efae4b558aaa34c288de7d6f2e926b4b | Vendor (CNA) |
| Linux Linux | e6e5a4cded9bef3a1b0a4fac815b7176eb9a18ec | Vendor (CNA) |
| debian:linux | 6.1.123-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- git.kernel.org/stable/c/23d742a3fcd4781eed015a3a93e6a0e3ab1ef2a8
- git.kernel.org/stable/c/2d194d951895df214e066d08146e77cb6e02c1d4
- git.kernel.org/stable/c/300e277e463e6326938dd55ea560eafa0f5c88a5
- git.kernel.org/stable/c/509ba8746f812e45a05034ba18b73db574693d11
- git.kernel.org/stable/c/5727343348f34e11a7c5a2a944d5aa505731d876
- git.kernel.org/stable/c/5bee35e5389f450a7eea7318deb9073e9414d3b1
- git.kernel.org/stable/c/a5a75207efae4b558aaa34c288de7d6f2e926b4b
- git.kernel.org/stable/c/e6e5a4cded9bef3a1b0a4fac815b7176eb9a18ec
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.