LiveActive security incident?Get immediate response
CVE Record

CVE-2024-53226: RDMA/hns: Fix NULL pointer derefernce in hns_roce_map_mr_sg()

In the Linux kernel, the following vulnerability has been resolved: RDMA/hns: Fix NULL pointer derefernce in hns_roce_map_mr_sg() ib_map_mr_sg() allows ULPs to specify NULL as the sg_offset argument. The driver needs to check whether it is a NULL pointer before dereferencing it.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Linux systems using the hns RoCE/RDMA driver may crash when kernel software supplies a missing offset pointer. The documented consequence is loss of availability; the supplied sources do not indicate data theft, modification, or code execution.

Executive priority

Patch promptly where hns RoCE/RDMA is present, especially on systems requiring high availability. Other Linux systems should first be inventoried because the supplied evidence does not show universal exposure or active exploitation.

Technical view

hns_roce_map_mr_sg() dereferences sg_offset without first checking for NULL, although ib_map_mr_sg() permits callers to provide NULL. This CWE-476 condition can cause a kernel NULL-pointer dereference and denial of service. Referenced Linux stable commits add the required check.

Likely exposure

Exposure is limited to Linux hosts running affected kernel code with the hns RoCE/RDMA driver relevant to their workload. The bundle does not define clean version ranges, so distribution backports and kernel package provenance must be checked.

Exploitation context

The bundle reports no KEV listing and provides no evidence of active exploitation or public weaponization. Although the CVSS vector rates the issue network-accessible without authentication, the cited material does not establish realistic remote triggerability or an internet attack path.

Researcher notes

The version data mixes commit hashes and release numbers under affected and unaffected statuses, including repeated identifiers. Treat it as record metadata rather than simple ranges. The sources establish the faulty dereference and correction, but provide limited detail about trigger prerequisites and remote reachability.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the referenced stable fix.
  • Check distribution security guidance for package-specific fixed versions and backports.
  • Prioritize availability-sensitive systems that actively use hns RoCE/RDMA functionality.

Validation and detection

  • Record each host's running kernel release and distribution package version.
  • Determine whether hns RoCE/RDMA hardware, modules, or workloads are present.
  • Verify the installed package changelog or advisory explicitly covers CVE-2024-53226.
  • Confirm the vendor kernel incorporates the applicable referenced stable fix.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-53226 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-53226Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxedc2dee07ab4ae2188b9780c453a64032162a5a0, 3c301b8a046b57e3de14c6fc669d81dcb71bb5b5, 5a13652ac34be9b60feec89835763574825a8905, 4d480e45cb7fffb9d9b49924469c1f458068080a, d387d4b54eb84208bd4ca13572e106851d0a0819, d387d4b54eb84208bd4ca13572e106851d0a0819, d387d4b54eb84208bd4ca13572e106851d0a0819, ecdf900a5a3372bc0208e0701a116f112eb6039c, 5.10.224, 5.15.165, 6.1.103, 6.6.44, 6.10.3unaffected
LinuxLinux6.11, 0, 5.10.231, 5.15.174, 6.1.120, 6.6.64, 6.11.11, 6.12.2, 6.13affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.