CVE-2024-26907: RDMA/mlx5: Fix fortify source warning while accessing Eth segment
Noroxi assessment
Priority: Monitor (action score 31/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 185fa07000e0a81d54cf8c05414cebff14469a5c, 4d5e86a56615cc387d21c629f9af8fb0e958d350, 60ba938a8bc8c90e724c75f98e932f9fb7ae1b9d.
Low priority for now. Upgrade to Linux Linux 185fa07000e0a81d54cf8c05414cebff14469a5c, 4d5e86a56615cc387d21c629f9af8fb0e958d350, 60ba938a8bc8c90e724c75f98e932f9fb7ae1b9d 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: RDMA/mlx5: Fix fortify source warning while accessing Eth segment ------------[ cut here ]------------ memcpy: detected field-spanning write (size 56) of single field "eseg->inline_hdr.start" at /var/lib/dkms/mlnx-ofed-kernel/5.8/build/drivers/infiniband/hw/mlx5/wr.c:131 (size 2) WARNING: CPU: 0 PID: 293779 at /var/lib/dkms/mlnx-ofed-kernel/5.8/build/drivers/infiniband/hw/mlx5/wr.c:131 mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] Modules linked in: 8021q garp mrp stp llc rdma_ucm(OE) rdma_cm(OE) iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_umad(OE) mlx5_ib(OE) ib_uverbs(OE) ib_core(OE) mlx5_core(OE) pci_hyperv_intf mlxdevm(OE) mlx_compat(OE) tls mlxfw(OE) psample nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink mst_pciconf(OE) knem(OE) vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd irqbypass cuse nfsv3 nfs fscache netfs xfrm_user xfrm_algo ipmi_devintf ipmi_msghandler binfmt_misc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 snd_pcsp aesni_intel crypto_simd cryptd snd_pcm snd_timer joydev snd soundcore input_leds serio_raw evbug nfsd auth_rpcgss nfs_acl lockd grace sch_fq_codel sunrpc drm efi_pstore ip_tables x_tables autofs4 psmouse virtio_net net_failover failover floppy [last unloaded: mlx_compat(OE)] CPU: 0 PID: 293779 Comm: ssh Tainted: G OE 6.2.0-32-generic #32~22.04.1-Ubuntu Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 RIP: 0010:mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] Code: 0c 01 00 a8 01 75 25 48 8b 75 a0 b9 02 00 00 00 48 c7 c2 10 5b fd c0 48 c7 c7 80 5b fd c0 c6 05 57 0c 03 00 01 e8 95 4d 93 da <0f> 0b 44 8b 4d b0 4c 8b 45 c8 48 8b 4d c0 e9 49 fb ff ff 41 0f b7 RSP: 0018:ffffb5b48478b570 EFLAGS: 00010046 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffffb5b48478b628 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffb5b48478b5e8 R13: ffff963a3c609b5e R14: ffff9639c3fbd800 R15: ffffb5b480475a80 FS: 00007fc03b444c80(0000) GS:ffff963a3dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000556f46bdf000 CR3: 0000000006ac6003 CR4: 00000000003706f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x72/0x90 ? mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] ? __warn+0x8d/0x160 ? mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] ? report_bug+0x1bb/0x1d0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x19/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? mlx5_ib_post_send+0x191b/0x1a60 [mlx5_ib] mlx5_ib_post_send_nodrain+0xb/0x20 [mlx5_ib] ipoib_send+0x2ec/0x770 [ib_ipoib] ipoib_start_xmit+0x5a0/0x770 [ib_ipoib] dev_hard_start_xmit+0x8e/0x1e0 ? validate_xmit_skb_list+0x4d/0x80 sch_direct_xmit+0x116/0x3a0 __dev_xmit_skb+0x1fd/0x580 __dev_queue_xmit+0x284/0x6b0 ? _raw_spin_unlock_irq+0xe/0x50 ? __flush_work.isra.0+0x20d/0x370 ? push_pseudo_header+0x17/0x40 [ib_ipoib] neigh_connected_output+0xcd/0x110 ip_finish_output2+0x179/0x480 ? __smp_call_single_queue+0x61/0xa0 __ip_finish_output+0xc3/0x190 ip_finish_output+0x2e/0xf0 ip_output+0x78/0x110 ? __pfx_ip_finish_output+0x10/0x10 ip_local_out+0x64/0x70 __ip_queue_xmit+0x18a/0x460 ip_queue_xmit+0x15/0x30 __tcp_transmit_skb+0x914/0x9c0 tcp_write_xmit+0x334/0x8d0 tcp_push_one+0x3c/0x60 tcp_sendmsg_locked+0x2e1/0xac0 tcp_sendmsg+0x2d/0x50 inet_sendmsg+0x43/0x90 sock_sendmsg+0x68/0x80 sock_write_iter+0x93/0x100 vfs_write+0x326/0x3c0 ksys_write+0xbd/0xf0 ? do_syscall_64+0x69/0x90 __x64_sys_write+0x19/0x30 do_syscall_ ---truncated---
- Published
- Apr 17, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 18th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 kernelbefore 5.10.214
- linux linux kernel5.11 and later · before 5.15.153
- linux linux kernel5.16 and later · before 6.1.83
- linux linux kernel6.2 and later · before 6.6.23
- linux linux kernel6.7 and later · before 6.7.11
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.0affected
- 34f4c9554d8b2a7d2deb9503e9373b598ee3279f and later · before d27c48dc309da72c3b46351a1205d89687272baaaffected · git
- 34f4c9554d8b2a7d2deb9503e9373b598ee3279f and later · before 60ba938a8bc8c90e724c75f98e932f9fb7ae1b9daffected · git
- 34f4c9554d8b2a7d2deb9503e9373b598ee3279f and later · before cad82f1671e41094acd3b9a60cd27d67a3c64a21affected · git
- 34f4c9554d8b2a7d2deb9503e9373b598ee3279f and later · before 9a624a5f95733bac4648ecadb320ca83aa9c08fdaffected · git
- 34f4c9554d8b2a7d2deb9503e9373b598ee3279f and later · before 185fa07000e0a81d54cf8c05414cebff14469a5caffected · git
- 34f4c9554d8b2a7d2deb9503e9373b598ee3279f and later · before 4d5e86a56615cc387d21c629f9af8fb0e958d350affected · git
- before 5.0not affected · semver
- 5.10.214 and later · up to and including 5.10.*not affected · semver
- 5.15.153 and later · up to and including 5.15.*not affected · semver
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.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.7.12-1 | 6.7.12-1 |
| Red Hat:rhel_eus:9.4::appstream | bpftool-debuginfo | before 0:7.3.0-427.70.1.el9_4 | 0:7.3.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel-matched | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-doc | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-427.70.1.el9_4 | 0:5.14.0-427.70.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-26903Apr 17, 2024 · Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security22Monitor
- ← EarlierCVE-2024-26906Apr 17, 2024 · x86/mm: Disallow vsyscall page read for copy_from_kernel_nofault()22Monitor
- Later →CVE-2023-52645Apr 17, 2024 · pmdomain: mediatek: fix race conditions with genpd18Monitor
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 | 185fa07000e0a81d54cf8c05414cebff14469a5c | Vendor (CNA) |
| Linux Linux | 4d5e86a56615cc387d21c629f9af8fb0e958d350 | Vendor (CNA) |
| Linux Linux | 60ba938a8bc8c90e724c75f98e932f9fb7ae1b9d | Vendor (CNA) |
| Linux Linux | 9a624a5f95733bac4648ecadb320ca83aa9c08fd | Vendor (CNA) |
| Linux Linux | cad82f1671e41094acd3b9a60cd27d67a3c64a21 | Vendor (CNA) |
| Linux Linux | d27c48dc309da72c3b46351a1205d89687272baa | Vendor (CNA) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.70.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.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.70.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.70.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.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (7 more)Show less
- git.kernel.org/stable/c/4d5e86a56615cc387d21c629f9af8fb0e958d350
- git.kernel.org/stable/c/60ba938a8bc8c90e724c75f98e932f9fb7ae1b9d
- git.kernel.org/stable/c/9a624a5f95733bac4648ecadb320ca83aa9c08fd
- git.kernel.org/stable/c/cad82f1671e41094acd3b9a60cd27d67a3c64a21
- git.kernel.org/stable/c/d27c48dc309da72c3b46351a1205d89687272baa
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.