CVE-2024-26638: nbd: always initialize struct msghdr completely
Noroxi assessment
Priority: Monitor (action score 17/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.22% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1960f2b534da1e6c65fb96f9e98bda773495f406, 78fbb92af27d0982634116c7a31065f24d092826, b0028f333420a65a53a63978522db680b37379dd.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1960f2b534da1e6c65fb96f9e98bda773495f406, 78fbb92af27d0982634116c7a31065f24d092826, b0028f333420a65a53a63978522db680b37379dd 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: nbd: always initialize struct msghdr completely syzbot complains that msg->msg_get_inq value can be uninitialized [1] struct msghdr got many new fields recently, we should always make sure their values is zero by default. [1] BUG: KMSAN: uninit-value in tcp_recvmsg+0x686/0xac0 net/ipv4/tcp.c:2571 tcp_recvmsg+0x686/0xac0 net/ipv4/tcp.c:2571 inet_recvmsg+0x131/0x580 net/ipv4/af_inet.c:879 sock_recvmsg_nosec net/socket.c:1044 [inline] sock_recvmsg+0x12b/0x1e0 net/socket.c:1066 __sock_xmit+0x236/0x5c0 drivers/block/nbd.c:538 nbd_read_reply drivers/block/nbd.c:732 [inline] recv_work+0x262/0x3100 drivers/block/nbd.c:863 process_one_work kernel/workqueue.c:2627 [inline] process_scheduled_works+0x104e/0x1e70 kernel/workqueue.c:2700 worker_thread+0xf45/0x1490 kernel/workqueue.c:2781 kthread+0x3ed/0x540 kernel/kthread.c:388 ret_from_fork+0x66/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242 Local variable msg created at: __sock_xmit+0x4c/0x5c0 drivers/block/nbd.c:513 nbd_read_reply drivers/block/nbd.c:732 [inline] recv_work+0x262/0x3100 drivers/block/nbd.c:863 CPU: 1 PID: 7465 Comm: kworker/u5:1 Not tainted 6.7.0-rc7-syzkaller-00041-gf016f7547aee #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Workqueue: nbd5-recv recv_work
- Published
- Mar 18, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-908
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 kernel5.19 and later · before 6.1.76
- linux linux kernel6.2 and later · before 6.6.15
- linux linux kernel6.7 and later · before 6.7.3
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.19affected
- f94fd25cb0aaf77fd7453f31c5d394a1a68ecf60 and later · before d9c54763e5cdbbd3f81868597fe8aca3c96e6387affected · git
- f94fd25cb0aaf77fd7453f31c5d394a1a68ecf60 and later · before 1960f2b534da1e6c65fb96f9e98bda773495f406affected · git
- f94fd25cb0aaf77fd7453f31c5d394a1a68ecf60 and later · before b0028f333420a65a53a63978522db680b37379ddaffected · git
- f94fd25cb0aaf77fd7453f31c5d394a1a68ecf60 and later · before 78fbb92af27d0982634116c7a31065f24d092826affected · git
- before 5.19not affected · semver
- 6.1.76 and later · up to and including 6.1.*not affected · semver
- 6.6.15 and later · up to and including 6.6.*not affected · semver
- 6.7.3 and later · up to and including 6.7.*not affected · semver
- 6.8 and laternot affected · original_commit_for_fix
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.76-1 | 6.1.76-1 |
| Debian:13 | linux | before 6.6.15-1 | 6.6.15-1 |
| Red Hat:rhel_eus:9.4::appstream | bpftool-debuginfo | before 0:7.3.0-427.74.1.el9_4 | 0:7.3.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel-matched | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-doc | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-427.74.1.el9_4 | 0:5.14.0-427.74.1.el9_4 |
+56
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-26636Mar 18, 2024 · llc: make llc_ui_sendmsg() more robust against bonding changes22Monitor
- ← EarlierCVE-2024-26637Mar 18, 2024 · wifi: ath11k: rely on mac80211 debugfs handling for vif22Monitor
- Later →CVE-2024-26640Mar 18, 2024 · tcp: add sanity checks to rx zerocopy22Monitor
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 | 1960f2b534da1e6c65fb96f9e98bda773495f406 | Vendor (CNA) |
| Linux Linux | 78fbb92af27d0982634116c7a31065f24d092826 | Vendor (CNA) |
| Linux Linux | b0028f333420a65a53a63978522db680b37379dd | Vendor (CNA) |
| Linux Linux | d9c54763e5cdbbd3f81868597fe8aca3c96e6387 | Vendor (CNA) |
| debian:linux | 6.1.76-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.74.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | 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.
- CVE-2024-50302246 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2024-47685217 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2024-2702244 days apartfork: defer linking file vma until vma is fully initialized31Monitor
- CVE-2021-4755367 days apartsched/scs: Reset task stack state in bringup_cpu()31Monitor
- CVE-2024-3689873 days apartgpiolib: cdev: fix uninitialised kfifo31Monitor
- CVE-2024-50143234 days apartudf: fix uninit-value use in udf_get_fileshortad31Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0205 · Mar 20, 2024(Linux Kernel Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-908 · Use of Uninitialized ResourceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.