RDMA/hfi1: Prevent use of lock before it is initialized
In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Prevent use of lock before it is initialized If there is a failure during probe of hfi1 before the sdma_map_lock is initialized, the call to hfi1_free_devdata() will attempt to use a lock that has not been initialized. If the locking correctness validator is on then an INFO message and stack trace resembling the following may be seen: INFO: trying to register non-static key. The code is fine but needs lockdep annotation, or maybe you didn't initialize this object before use? turning off the locking correctness validator. Call Trace: register_lock_class+0x11b/0x880 __lock_acquire+0xf3/0x7930 lock_acquire+0xff/0x2d0 _raw_spin_lock_irq+0x46/0x60 sdma_clean+0x42a/0x660 [hfi1] hfi1_free_devdata+0x3a7/0x420 [hfi1] init_one+0x867/0x11a0 [hfi1] pci_device_probe+0x40e/0x8d0 The use of sdma_map_lock in sdma_clean() is for freeing the sdma_map memory, and sdma_map is not allocated/initialized until after sdma_map_lock has been initialized. This code only needs to be run if sdma_map is not NULL, and so checking for that condition will avoid trying to use the lock before it is initialized.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 17th percentile
- CWE
- CWE-908
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
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.3%
Affected systems
| 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 kernel4.3 and later · before 4.19.247
- linux linux kernel4.20 and later · before 5.4.198
- linux linux kernel5.5 and later · before 5.10.121
- linux linux kernel5.11 and later · before 5.15.46
- linux linux kernel5.16 and later · before 5.17.14
- linux linux kernel5.18 and later · before 5.18.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
- 4.3affected
- 7724105686e718ac476a6ad3304fea2fbcfcffde and later · before 66090815a24ce14cf51ef5453fc0218fe8a39bc2affected · git
- 7724105686e718ac476a6ad3304fea2fbcfcffde and later · before addb192000d8819c0b1553453994df9bb54c28dbaffected · git
- 7724105686e718ac476a6ad3304fea2fbcfcffde and later · before fc0750e659db7b315bf6348902cc8ca3cdd4b8d8affected · git
- 7724105686e718ac476a6ad3304fea2fbcfcffde and later · before ca55150bff5817af4f857a746ecab9862c23e12aaffected · git
- 7724105686e718ac476a6ad3304fea2fbcfcffde and later · before 30eb275e7ed588270ae159cc590a96658e0cfd8faffected · git
- 7724105686e718ac476a6ad3304fea2fbcfcffde and later · before 288d198f50434f29b4a26a9de4394ae2305ad8afaffected · git
- 7724105686e718ac476a6ad3304fea2fbcfcffde and later · before 05c03dfd09c069c4ffd783b47b2da5dcc9421f2caffected · git
- before 4.3not affected · semver
- 4.19.247 and later · up to and including 4.19.*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 5.18.5-1 | 5.18.5-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
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 05c03dfd09c069c4ffd783b47b2da5dcc9421f2c | Vendor (CNA) |
| Linux Linux | 288d198f50434f29b4a26a9de4394ae2305ad8af | Vendor (CNA) |
| Linux Linux | 30eb275e7ed588270ae159cc590a96658e0cfd8f | Vendor (CNA) |
| Linux Linux | 66090815a24ce14cf51ef5453fc0218fe8a39bc2 | Vendor (CNA) |
| Linux Linux | addb192000d8819c0b1553453994df9bb54c28db | Vendor (CNA) |
| Linux Linux | ca55150bff5817af4f857a746ecab9862c23e12a | Vendor (CNA) |
| Linux Linux | fc0750e659db7b315bf6348902cc8ca3cdd4b8d8 | Vendor (CNA) |
| debian:linux | 5.18.5-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-2024-50302100 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2026-52989483 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers39Monitor
- CVE-2024-47685128 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2026-53225484 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()36Monitor
- CVE-2026-53170484 days apartaccel/ethosu: reject DMA commands with uninitialized length35Monitor
- CVE-2026-43139434 days apartxfrm6: fix uninitialized saddr in xfrm6_get_saddr()34Monitor
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)
CWE-908 · Use of Uninitialized ResourceCVSS 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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/05c03dfd09c069c4ffd783b47b2da5dcc9421f2c
- git.kernel.org/stable/c/288d198f50434f29b4a26a9de4394ae2305ad8af
- git.kernel.org/stable/c/30eb275e7ed588270ae159cc590a96658e0cfd8f
- git.kernel.org/stable/c/66090815a24ce14cf51ef5453fc0218fe8a39bc2
- git.kernel.org/stable/c/addb192000d8819c0b1553453994df9bb54c28db
- git.kernel.org/stable/c/ca55150bff5817af4f857a746ecab9862c23e12a
- git.kernel.org/stable/c/fc0750e659db7b315bf6348902cc8ca3cdd4b8d8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.