CyberSecBulletin
CVE-2026-43150NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-43150 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 7e2c200010aa93fa78201da959b4ac6b9f8fed0b, d3e837e11ee9ed08df229272319199003ba00379, 00d69f21ef2ab00e6156c764d89e2b3539eb2f33 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.14% 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 7e2c200010aa93fa78201da959b4ac6b9f8fed0b or d3e837e11ee9ed08df229272319199003ba00379 or 00d69f21ef2ab00e6156c764d89e2b3539eb2f33 or 08c7eadd8a934a1968e1aeeee8b61b853b99fb3a, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.165 or 6.6.128 or 6.12.75 or 6.18.16, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux28fa550a49e818d6445e787f584759b1bf21d9d4 up to, but not including, 7e2c200010aa93fa78201da959b4ac6b9f8fed0b; 7819e05a0dceac20c5ff78ec9b252faf3b76b824 up to, but not including, d3e837e11ee9ed08df229272319199003ba00379; 7819e05a0dceac20c5ff78ec9b252faf3b76b824 up to, but not including, 00d69f21ef2ab00e6156c764d89e2b3539eb2f33; 7819e05a0dceac20c5ff78ec9b252faf3b76b824 up to, but not including, 08c7eadd8a934a1968e1aeeee8b61b853b99fb3a; 7819e05a0dceac20c5ff78ec9b252faf3b76b824 up to, but not including, a251d866f50b6a4c95901fa722025065679c2eca; 7819e05a0dceac20c5ff78ec9b252faf3b76b824 up to, but not including, 36c0de02575ce59dfd879eb4ef63d53a68bbf9ce; 6.1.63 up to, but not including, 6.1.165; 6.57e2c200010aa93fa78201da959b4ac6b9f8fed0b, d3e837e11ee9ed08df229272319199003ba00379, 00d69f21ef2ab00e6156c764d89e2b3539eb2f33, 08c7eadd8a934a1968e1aeeee8b61b853b99fb3a, a251d866f50b6a4c95901fa722025065679c2eca, 36c0de02575ce59dfd879eb4ef63d53a68bbf9ce
LinuxLinux Kernel6.1.63 up to, but not including, 6.1.165; 6.5 up to, but not including, 6.6.128; 6.7 up to, but not including, 6.12.75; 6.13 up to, but not including, 6.18.16; 6.19 up to, but not including, 6.19.66.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6

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.17.8HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: perf/arm-cmn: Reject unsupported hardware configurations So far we've been fairly lax about accepting both unknown CMN models (at least with a warning), and unknown revisions of those which we do know, as although things do frequently change between releases, typically enough remains the same to be somewhat useful for at least some basic bringup checks. However, we also make assumptions of the maximum supported sizes and numbers of things in various places, and there's no guarantee that something new might not be bigger and lead to nasty array overflows. Make sure we only try to run on things that actually match our assumptions and so will not risk memory corruption. We have at least always failed on completely unknown node types, so update that error message for clarity and consistency too.

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. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.