Skip to content
Noroxi
CVE-2022-49433· NVD / CVE Program· CNA Linux

RDMA/hfi1: Prevent use of lock before it is initialized

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 05c03dfd09c069c4ffd783b47b2da5dcc9421f2c, 288d198f50434f29b4a26a9de4394ae2305ad8af, 30eb275e7ed588270ae159cc590a96658e0cfd8f.

Low priority for now. Upgrade to Linux Linux 05c03dfd09c069c4ffd783b47b2da5dcc9421f2c, 288d198f50434f29b4a26a9de4394ae2305ad8af, 30eb275e7ed588270ae159cc590a96658e0cfd8f 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 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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 18th percentile

Report tools

JSON

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.

Follow CVE-2022-49433

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.18.5-15.18.5-1

Same product

linux: all records

Other 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • 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 haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-49431Feb 26, 2025 · powerpc/iommu: Add missing of_node_put in iommu_init_early_dart
    22Monitor
  • ← EarlierCVE-2022-49432Feb 26, 2025 · powerpc/xics: fix refcount leak in icp_opal_init()
    22Monitor
  • Later →CVE-2022-49434Feb 26, 2025 · PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux05c03dfd09c069c4ffd783b47b2da5dcc9421f2cVendor (CNA)
Linux Linux288d198f50434f29b4a26a9de4394ae2305ad8afVendor (CNA)
Linux Linux30eb275e7ed588270ae159cc590a96658e0cfd8fVendor (CNA)
Linux Linux66090815a24ce14cf51ef5453fc0218fe8a39bc2Vendor (CNA)
Linux Linuxaddb192000d8819c0b1553453994df9bb54c28dbVendor (CNA)
Linux Linuxca55150bff5817af4f857a746ecab9862c23e12aVendor (CNA)
Linux Linuxfc0750e659db7b315bf6348902cc8ca3cdd4b8d8Vendor (CNA)
debian:linux5.18.5-1 · Debian:12Package 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.

EPSS, last 120 days

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 researchers

Finders, 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-5030299 days apartHID: core: zero-initialize the report bufferKEV
    52Plan
  • CVE-2026-52989483 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers
    39Monitor
  • 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 length
    35Monitor
  • 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 Resource

CVSS 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records