Skip to main content
VulnerabilityPublished Updated

CVE-2026-43350: Linux kernel · Out-of-bounds Read

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.6 High · fixed in f8488c07bea2431ee12a6067d736578064fa46b4 : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:07 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f8488c07bea2431ee12a6067d736578064fa46b4, c8eef12af1cc73031639ea7cf16e0b10e2536b0b, b53b8e98c23310294fc45fc686db5ee860311896 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e2f8fbfb8d09c06decde162090fac3ee220aa280, < f8488c07bea2431ee12a6067d736578064fa46b4
Fixed in
  • f8488c07bea2431ee12a6067d736578064fa46b4
LinuxLinuxAffected
  • ≥ e2f8fbfb8d09c06decde162090fac3ee220aa280, < c8eef12af1cc73031639ea7cf16e0b10e2536b0b
Fixed in
  • c8eef12af1cc73031639ea7cf16e0b10e2536b0b
LinuxLinuxAffected
  • ≥ e2f8fbfb8d09c06decde162090fac3ee220aa280, < b53b8e98c23310294fc45fc686db5ee860311896
Fixed in
  • b53b8e98c23310294fc45fc686db5ee860311896
LinuxLinuxAffected
  • ≥ e2f8fbfb8d09c06decde162090fac3ee220aa280, < 2757ad3e4b6f9e0fed4c7739594e702abc5cab21
Fixed in
  • 2757ad3e4b6f9e0fed4c7739594e702abc5cab21
LinuxLinuxAffected
  • ≥ e2f8fbfb8d09c06decde162090fac3ee220aa280, < 1592a6cd6f653f2d24572a6976c7a775b19f4940
Fixed in
  • 1592a6cd6f653f2d24572a6976c7a775b19f4940
LinuxLinuxAffected
  • ≥ e2f8fbfb8d09c06decde162090fac3ee220aa280, < 38a69f08ee82c450d3e4168707fff2e317dc3ff7
Fixed in
  • 38a69f08ee82c450d3e4168707fff2e317dc3ff7

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: require a full NFS mode SID before reading mode bits parse_dacl() treats an ACE SID matching sid_unix_NFS_mode as an NFS mode SID and reads sid.sub_auth[2] to recover the mode bits. That assumes the ACE carries three subauthorities, but compare_sids() only compares min(a, b) subauthorities. A malicious server can return an ACE with num_subauth = 2 and sub_auth[] = {88, 3}, which still matches sid_unix_NFS_mode and then drives the sub_auth[2] read four bytes past the end of the ACE. Require num_subauth >= 3 before treating the ACE as an NFS mode SID. This keeps the fix local to the special-SID mode path without changing compare_sids() semantics for the rest of cifsacl.

References

Community reviews

Loading reviews…