dbcve.org
Linux KernelOperating system · Linux

CVE-2026-52967

HIGH · 8.1 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.1.175 / 6.6.141 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: smb/client: fix possible infinite loop and oob read in symlink_data() On 32-bit architectures, the infinite loop is as follows: len = p->ErrorDataLength == 0xfffffff8 u8 *next = p->ErrorContextData + len next == p On 32-bit architectures, the out-of-bounds read is as follows: len = p->ErrorDataLength == 0xfffffff0 u8 *next = p->ErrorContextData + len next == (u8 *)p - 8

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the Linux kernel's SMB client symlink_data() function allows infinite loops and out-of-bounds memory reads on 32-bit architectures. When ErrorDataLength is set to specific values (0xfffffff8 or 0xfffffff0), pointer arithmetic causes the loop iterator to either point back to the current structure (infinite loop) or to memory before the current pointer (OOB read).

MitigationApply the corresponding kernel patch which adds bounds validation on ErrorDataLength before performing pointer arithmetic. Update Linux kernels on affected 32-bit systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.0.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine system architecture
    Run 'uname -m' to check if the system is 32-bit (i686, i386, or armv7l indicates 32-bit). The vulnerability only affects 32-bit architectures.
    Affected if Architecture is 32-bit (i686, i386, armv7l, or similar)
  2. Check kernel version
    Run 'uname -r' to get the kernel version. Compare it against the affected ranges: >= 6.0.16 and < 6.1.175; >= 6.2 and < 6.6.141; >= 6.7 and < 6.12.91; >= 6.13 and < 6.18.33; >= 6.19 and < 7.0.10; or exactly version 7.1
    Affected if Kernel version falls within any of the affected version ranges listed in the CVE
  3. Verify SMB client is in use
    Run 'lsmod | grep -E "cifs|smb"' to check if the CIFS/SMB client kernel module is loaded. Also check if any SMB shares are mounted via 'mount | grep -i cifs' or 'mount | grep -i smb'
    Affected if The cifs kernel module is loaded AND SMB shares are mounted from a remote server
  4. Check for symlink handling in SMB
    Inspect if the system processes SMB symlinks. This is a feature in the SMB client code (symlink_data function). There is no direct config flag to check, but the vulnerability is in the SMB2/symlink handling code path.
    Affected if The SMB client processes server-provided symbolic links (SMB2 reparse points)

A system is affected if it is 32-bit architecture, runs an affected kernel version, and uses the CIFS/SMB client to mount remote shares.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.1.175 / 6.6.141 / 6.12.91 or later
Fixed in 6.1.1756.6.1416.12.91
Interim mitigation

Apply the corresponding kernel patch which adds bounds validation on ErrorDataLength before performing pointer arithmetic. Update Linux kernels on affected 32-bit systems.

Recommended fix High confidence

6.1.175+, 6.6.141+, 6.12.91+, or 6.18.33+ depending on your current branch

  1. 1. Identify the currently running kernel version using `uname -r`
  2. 2. Determine which kernel branch your system is using (e.g., 6.1.y, 6.6.y, 6.7.y, 6.12.y, or 6.13.y)
  3. 3. Upgrade the Linux kernel to a fixed version based on your current branch: for 6.1.x upgrade to >= 6.1.175, for 6.2-6.6.x upgrade to >= 6.6.141, for 6.7-6.12.x upgrade to >= 6.12.91, for 6.13+ upgrade to >= 6.18.33
  4. 4. On Debian/Ubuntu: `apt-get update && apt-get dist-upgrade` or install specific kernel package
  5. 5. On RHEL/CentOS: `yum update kernel` or `dnf update kernel`
  6. 6. On SUSE: `zypper update kernel-default`
  7. 7. After upgrade, reboot the system to load the new kernel: `reboot`
  8. 8. Verify the new kernel is running with `uname -r` and confirm the version includes the fix
Caveat Kernel upgrades may require matching system utilities or drivers; test in staging first for production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA6.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52967 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data