IB/core: Fix ib_cache_setup_one error flow cleanup
Noroxi assessment
Priority: Monitor (action score 26/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.98% (FIRST EPSS); higher than 61.9% of all records.
- Anyone who can reach it over the internet 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 1403c8b14765eab805377dd3b75e96ace8747aed, 1730d47d1865af89efd01cf0469a9a739cbf60f2, 290fe42fe0165205c4451334d8833a9202ae1d52; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5.
Low priority for now. Upgrade to Linux Linux 1403c8b14765eab805377dd3b75e96ace8747aed, 1730d47d1865af89efd01cf0469a9a739cbf60f2, 290fe42fe0165205c4451334d8833a9202ae1d52; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5 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: IB/core: Fix ib_cache_setup_one error flow cleanup When ib_cache_update return an error, we exit ib_cache_setup_one instantly with no proper cleanup, even though before this we had already successfully done gid_table_setup_one, that results in the kernel WARN below. Do proper cleanup using gid_table_cleanup_one before returning the err in order to fix the issue. WARNING: CPU: 4 PID: 922 at drivers/infiniband/core/cache.c:806 gid_table_release_one+0x181/0x1a0 Modules linked in: CPU: 4 UID: 0 PID: 922 Comm: c_repro Not tainted 6.11.0-rc1+ #3 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:gid_table_release_one+0x181/0x1a0 Code: 44 8b 38 75 0c e8 2f cb 34 ff 4d 8b b5 28 05 00 00 e8 23 cb 34 ff 44 89 f9 89 da 4c 89 f6 48 c7 c7 d0 58 14 83 e8 4f de 21 ff <0f> 0b 4c 8b 75 30 e9 54 ff ff ff 48 8 3 c4 10 5b 5d 41 5c 41 5d 41 RSP: 0018:ffffc90002b835b0 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff811c8527 RDX: 0000000000000000 RSI: ffffffff811c8534 RDI: 0000000000000001 RBP: ffff8881011b3d00 R08: ffff88810b3abe00 R09: 205d303839303631 R10: 666572207972746e R11: 72746e6520444947 R12: 0000000000000001 R13: ffff888106390000 R14: ffff8881011f2110 R15: 0000000000000001 FS: 00007fecc3b70800(0000) GS:ffff88813bd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020000340 CR3: 000000010435a001 CR4: 00000000003706b0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? show_regs+0x94/0xa0 ? __warn+0x9e/0x1c0 ? gid_table_release_one+0x181/0x1a0 ? report_bug+0x1f9/0x340 ? gid_table_release_one+0x181/0x1a0 ? handle_bug+0xa2/0x110 ? exc_invalid_op+0x31/0xa0 ? asm_exc_invalid_op+0x16/0x20 ? __warn_printk+0xc7/0x180 ? __warn_printk+0xd4/0x180 ? gid_table_release_one+0x181/0x1a0 ib_device_release+0x71/0xe0 ? __pfx_ib_device_release+0x10/0x10 device_release+0x44/0xd0 kobject_put+0x135/0x3d0 put_device+0x20/0x30 rxe_net_add+0x7d/0xa0 rxe_newlink+0xd7/0x190 nldev_newlink+0x1b0/0x2a0 ? __pfx_nldev_newlink+0x10/0x10 rdma_nl_rcv_msg+0x1ad/0x2e0 rdma_nl_rcv_skb.constprop.0+0x176/0x210 netlink_unicast+0x2de/0x400 netlink_sendmsg+0x306/0x660 __sock_sendmsg+0x110/0x120 ____sys_sendmsg+0x30e/0x390 ___sys_sendmsg+0x9b/0xf0 ? kstrtouint+0x6e/0xa0 ? kstrtouint_from_user+0x7c/0xb0 ? get_pid_task+0xb0/0xd0 ? proc_fail_nth_write+0x5b/0x140 ? __fget_light+0x9a/0x200 ? preempt_count_add+0x47/0xa0 __sys_sendmsg+0x61/0xd0 do_syscall_64+0x50/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 61th percentile
- CWE
- CWE-459
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
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.4.42 and later · before 5.15.168
- linux linux kernel5.16 and later · before 6.1.113
- linux linux kernel6.2 and later · before 6.6.54
- linux linux kernel6.7 and later · before 6.10.13
- linux linux kernel6.11 and later · before 6.11.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
- ee7ce7d7e7c76d5ec4c8067d32bbee9728dc9d29, 2a5968f266c7b9dc13917ac573af8d7b7da4023c, 5.7affected
- 1901b91f99821955eac2bd48fe25ee983385dc00 and later · before 1730d47d1865af89efd01cf0469a9a739cbf60f2affected · git
- 1901b91f99821955eac2bd48fe25ee983385dc00 and later · before 45f63f4bb9a7128a6209d766c2fc02b3d42fbf3eaffected · git
- 1901b91f99821955eac2bd48fe25ee983385dc00 and later · before d08754be993f270e3d296d8f5d8e071fe6638651affected · git
- 1901b91f99821955eac2bd48fe25ee983385dc00 and later · before af633fd9d9fff59e31c804f47ca0c8a784977773affected · git
- 1901b91f99821955eac2bd48fe25ee983385dc00 and later · before 290fe42fe0165205c4451334d8833a9202ae1d52affected · git
- 1901b91f99821955eac2bd48fe25ee983385dc00 and later · before 1403c8b14765eab805377dd3b75e96ace8747aedaffected · git
- 5.4.42 and later · before 5.5affected · semver
- 5.6.14 and later · before 5.7affected · semver
- before 5.7not 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.115-1 | 6.1.115-1 |
| Debian:13 | linux | before 6.11.2-1 | 6.11.2-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2024-47690Oct 21, 2024 · f2fs: get rid of online repaire on corrupted directory22Monitor
- ← EarlierCVE-2024-47691Oct 21, 2024 · f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()31Monitor
- Later →CVE-2024-47694Oct 21, 2024 · IB/mlx5: Fix UMR pd cleanup on error flow of driver init22Monitor
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 | 1403c8b14765eab805377dd3b75e96ace8747aed | Vendor (CNA) |
| Linux Linux | 1730d47d1865af89efd01cf0469a9a739cbf60f2 | Vendor (CNA) |
| Linux Linux | 290fe42fe0165205c4451334d8833a9202ae1d52 | Vendor (CNA) |
| Linux Linux | 45f63f4bb9a7128a6209d766c2fc02b3d42fbf3e | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5.7 | Vendor (CNA) |
| Linux Linux | af633fd9d9fff59e31c804f47ca0c8a784977773 | Vendor (CNA) |
| Linux Linux | d08754be993f270e3d296d8f5d8e071fe6638651 | Vendor (CNA) |
| Azure Linux 3.0 ARM | 6.6.56.1-5 · kernel | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 6.6.56.1-5 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 ARM | 5.15.173.1-1 · kernel | Microsoft (MSRC) |
| CBL Mariner 2.0 x64 | 5.15.173.1-1 · kernel | Microsoft (MSRC) |
| debian:linux | 6.1.115-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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-2025-37908211 days apartmm, slab: clean up slab->obj_exts always31Monitor
- CVE-2021-47110220 days apartx86/kvm: Disable kvmclock on all CPUs on shutdown28Monitor
- CVE-2022-490120 days apartafs: Fix server->active leak in afs_put_server22Monitor
- CVE-2022-490280 days apartixgbevf: Fix resource leak in ixgbevf_init_module()22Monitor
- CVE-2024-477280 days apartbpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error22Monitor
- CVE-2024-477310 days apartdrivers/perf: Fix ali_drw_pmu driver interrupt status clearing22Monitor
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
- Anyone who can reach it over the internet 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
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-459 · Incomplete CleanupCVSS vector
CVSS:3.1/AV:N/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 (6 more)Show less
- git.kernel.org/stable/c/1730d47d1865af89efd01cf0469a9a739cbf60f2
- git.kernel.org/stable/c/290fe42fe0165205c4451334d8833a9202ae1d52
- git.kernel.org/stable/c/45f63f4bb9a7128a6209d766c2fc02b3d42fbf3e
- git.kernel.org/stable/c/af633fd9d9fff59e31c804f47ca0c8a784977773
- git.kernel.org/stable/c/d08754be993f270e3d296d8f5d8e071fe6638651
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.