CVE-2024-36478: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues'
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.26% (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 1d4c8baef435c98e8d5aa7027dc5a9f70834ba16, 5d0495473ee4c1d041b5a917f10446a22c047f47, a2db328b0839312c169eb42746ec46fc1ab53ed2; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.57.1-1.
Low priority for now. Upgrade to Linux Linux 1d4c8baef435c98e8d5aa7027dc5a9f70834ba16, 5d0495473ee4c1d041b5a917f10446a22c047f47, a2db328b0839312c169eb42746ec46fc1ab53ed2; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.57.1-1 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: null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' Writing 'power' and 'submit_queues' concurrently will trigger kernel panic: Test script: modprobe null_blk nr_devices=0 mkdir -p /sys/kernel/config/nullb/nullb0 while true; do echo 1 > submit_queues; echo 4 > submit_queues; done & while true; do echo 1 > power; echo 0 > power; done Test result: BUG: kernel NULL pointer dereference, address: 0000000000000148 Oops: 0000 [#1] PREEMPT SMP RIP: 0010:__lock_acquire+0x41d/0x28f0 Call Trace: <TASK> lock_acquire+0x121/0x450 down_write+0x5f/0x1d0 simple_recursive_removal+0x12f/0x5c0 blk_mq_debugfs_unregister_hctxs+0x7c/0x100 blk_mq_update_nr_hw_queues+0x4a3/0x720 nullb_update_nr_hw_queues+0x71/0xf0 [null_blk] nullb_device_submit_queues_store+0x79/0xf0 [null_blk] configfs_write_iter+0x119/0x1e0 vfs_write+0x326/0x730 ksys_write+0x74/0x150 This is because del_gendisk() can concurrent with blk_mq_update_nr_hw_queues(): nullb_device_power_store nullb_apply_submit_queues null_del_dev del_gendisk nullb_update_nr_hw_queues if (!dev->nullb) // still set while gendisk is deleted return 0 blk_mq_update_nr_hw_queues dev->nullb = NULL Fix this problem by resuing the global mutex to protect nullb_device_power_store() and nullb_update_nr_hw_queues() from configfs.
- Published
- Jun 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-476
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 |
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
- 5.5affected
- 45919fbfe1c487c17ea1d198534339a5e8abeae3 and later · before 1d4c8baef435c98e8d5aa7027dc5a9f70834ba16affected · git
- 45919fbfe1c487c17ea1d198534339a5e8abeae3 and later · before aaadb755f2d684f715a6eb85cb7243aa0c67dfa9affected · git
- 45919fbfe1c487c17ea1d198534339a5e8abeae3 and later · before 5d0495473ee4c1d041b5a917f10446a22c047f47affected · git
- 45919fbfe1c487c17ea1d198534339a5e8abeae3 and later · before a2db328b0839312c169eb42746ec46fc1ab53ed2affected · git
- before 5.5not affected · semver
- 6.1.119 and later · up to and including 6.1.*not affected · semver
- 6.6.55 and later · up to and including 6.6.*not affected · semver
- 6.9.4 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.5 and later · before 6.9.4
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.119-1 | 6.1.119-1 |
| Debian:13 | linux | before 6.9.7-1 | 6.9.7-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-36244Jun 21, 2024 · net/sched: taprio: extend minimum interval restriction to entire cycle too22Monitor
- ← EarlierCVE-2024-36281Jun 21, 2024 · net/mlx5: Use mlx5_ipsec_rx_status_destroy to correctly delete status rules22Monitor
- Later →CVE-2024-38388Jun 21, 2024 · ALSA: hda/cs_dsp_ctl: Use private_free for control cleanup31Monitor
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 | 1d4c8baef435c98e8d5aa7027dc5a9f70834ba16 | Vendor (CNA) |
| Linux Linux | 5d0495473ee4c1d041b5a917f10446a22c047f47 | Vendor (CNA) |
| Linux Linux | a2db328b0839312c169eb42746ec46fc1ab53ed2 | Vendor (CNA) |
| Linux Linux | aaadb755f2d684f715a6eb85cb7243aa0c67dfa9 | Vendor (CNA) |
| azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 | 6.6.57.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.57.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.119-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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)
CWE-476 · NULL Pointer DereferenceCVSS 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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.