CVE-2022-49429: RDMA/hfi1: Prevent panic when SDMA is disabled
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 0e4dda8b3f4c07ee9ea670a10ea3171a5e63a86f, 22e7e400fd1a890db2ea13686324aff50e972f4f, 29952ab85d6c3fe0b7909d9a737f10c58bf6824d.
Low priority for now. Upgrade to Linux Linux 0e4dda8b3f4c07ee9ea670a10ea3171a5e63a86f, 22e7e400fd1a890db2ea13686324aff50e972f4f, 29952ab85d6c3fe0b7909d9a737f10c58bf6824d 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/hfi1: Prevent panic when SDMA is disabled If the hfi1 module is loaded with HFI1_CAP_SDMA off, a call to hfi1_write_iter() will dereference a NULL pointer and panic. A typical stack frame is: sdma_select_user_engine [hfi1] hfi1_user_sdma_process_request [hfi1] hfi1_write_iter [hfi1] do_iter_readv_writev do_iter_write vfs_writev do_writev do_syscall_64 The fix is to test for SDMA in hfi1_write_iter() and fail the I/O with EINVAL.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- CWE-476
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.2%
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 4.14.283
- linux linux kernel4.15 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.9affected
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before 33794e8e9bcb4affc0ebff9cdec85acc8b8a1762affected · git
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before 0e4dda8b3f4c07ee9ea670a10ea3171a5e63a86faffected · git
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before e60ad83f645ee6fadd5a8057ba267aeec54f08feaffected · git
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before cc80d3c37cec9d6ddb140483647901bc7cc6c31daffected · git
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before 32e6aea33944f364d51cd263e4cd236393a188b6affected · git
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before 29952ab85d6c3fe0b7909d9a737f10c58bf6824daffected · git
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before 22e7e400fd1a890db2ea13686324aff50e972f4faffected · git
- 0cb2aa690c7ef14ad1f544288349abb5434bb75d and later · before 629e052d0c98e46dde9f0824f0aa437f678d9b8faffected · git
- before 4.9not 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-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-2022-49427Feb 26, 2025 · iommu/mediatek: Remove clk_disable in mtk_iommu_remove22Monitor
- ← EarlierCVE-2022-49428Feb 26, 2025 · f2fs: fix to do sanity check on inline_dots inode22Monitor
- Later →CVE-2022-49430Feb 26, 2025 · Input: gpio-keys - cancel delayed work only in case of GPIO22Monitor
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 | 0e4dda8b3f4c07ee9ea670a10ea3171a5e63a86f | Vendor (CNA) |
| Linux Linux | 22e7e400fd1a890db2ea13686324aff50e972f4f | Vendor (CNA) |
| Linux Linux | 29952ab85d6c3fe0b7909d9a737f10c58bf6824d | Vendor (CNA) |
| Linux Linux | 32e6aea33944f364d51cd263e4cd236393a188b6 | Vendor (CNA) |
| Linux Linux | 33794e8e9bcb4affc0ebff9cdec85acc8b8a1762 | Vendor (CNA) |
| Linux Linux | 629e052d0c98e46dde9f0824f0aa437f678d9b8f | Vendor (CNA) |
| Linux Linux | cc80d3c37cec9d6ddb140483647901bc7cc6c31d | Vendor (CNA) |
| Linux Linux | e60ad83f645ee6fadd5a8057ba267aeec54f08fe | 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.
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
- 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/22e7e400fd1a890db2ea13686324aff50e972f4f
- git.kernel.org/stable/c/29952ab85d6c3fe0b7909d9a737f10c58bf6824d
- git.kernel.org/stable/c/32e6aea33944f364d51cd263e4cd236393a188b6
- git.kernel.org/stable/c/33794e8e9bcb4affc0ebff9cdec85acc8b8a1762
- git.kernel.org/stable/c/629e052d0c98e46dde9f0824f0aa437f678d9b8f
- git.kernel.org/stable/c/cc80d3c37cec9d6ddb140483647901bc7cc6c31d
- git.kernel.org/stable/c/e60ad83f645ee6fadd5a8057ba267aeec54f08fe
Vendor advisories and official records. Exploit/PoC links are deliberately left out.