CyberSecBulletin
CVE-2025-37943NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2025-37943 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 7f1d986da5c6abb75ffe4d0d325fc9b341c41a1c, 3abe15e756481c45f6acba3d476cb3ca4afc3b61, 6ee653194ddb83674913fd2727b8ecfae0597ade as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 7f1d986da5c6abb75ffe4d0d325fc9b341c41a1c or 3abe15e756481c45f6acba3d476cb3ca4afc3b61 or 6ee653194ddb83674913fd2727b8ecfae0597ade or 50be1fb76556e80af9f5da80f28168b6c71bce58, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.88 or 6.12.24 or 6.13.12 or 6.14.3, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxd889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 7f1d986da5c6abb75ffe4d0d325fc9b341c41a1c; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 3abe15e756481c45f6acba3d476cb3ca4afc3b61; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 6ee653194ddb83674913fd2727b8ecfae0597ade; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 50be1fb76556e80af9f5da80f28168b6c71bce58; d889913205cf7ebda905b1e62c5867ed4e39f6c2 up to, but not including, 9a0dddfb30f120db3851627935851d262e4e7acb; 6.37f1d986da5c6abb75ffe4d0d325fc9b341c41a1c, 3abe15e756481c45f6acba3d476cb3ca4afc3b61, 6ee653194ddb83674913fd2727b8ecfae0597ade, 50be1fb76556e80af9f5da80f28168b6c71bce58, 9a0dddfb30f120db3851627935851d262e4e7acb
LinuxLinux Kernel6.3 up to, but not including, 6.6.88; 6.7 up to, but not including, 6.12.24; 6.13 up to, but not including, 6.13.12; 6.14 up to, but not including, 6.14.36.6.88, 6.12.24, 6.13.12, 6.14.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi In certain cases, hardware might provide packets with a length greater than the maximum native Wi-Fi header length. This can lead to accessing and modifying fields in the header within the ath12k_dp_rx_h_undecap_nwifi function for DP_RX_DECAP_TYPE_NATIVE_WIFI decap type and potentially resulting in invalid data access and memory corruption. Add a sanity check before processing the SKB to prevent invalid data access in the undecap native Wi-Fi function for the DP_RX_DECAP_TYPE_NATIVE_WIFI decap type. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.