BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-53250High confidence

xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 14 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.10% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

25 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.111-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.111-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.13-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-53250 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2026-53250
46 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path. Fix this by reading csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment. Note that other metadata fields (flags, launch_time) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-39201

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path. Fix this by reading csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment. Note that other metadata fields (flags, launch_time) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path. Fix this by reading csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment. Note that other metadata fields (flags, launch_time) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.

What

In the Linux kernel, the following vulnerability has been resolved: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path. Fix this by reading csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment. Note that other metadata fields (flags, launch_time) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path. Fix this by reading csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment. Note that other metadata fields (flags, launch_time) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.

Why

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Time-of-check Time-of-use (TOCTOU) Race Condition → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-367 ↗

CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-367
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-39201Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata() The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path. Fix this by reading csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment. Note that other metadata fields (flags, launch_time) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53240 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53244 https://www.cve.org/CVERecord?id=CVE-2026-53244 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53247 https://www.cve.org/CVERecord?id=CVE-2026-53247 Référence CVE CVE-2026-53248 https://www.cve.org/CVERecord?id=CVE-2026-53248 Référence CVE CVE-2026-53249 https://www.cve.org/CVERecord?id=CVE-2026-53249 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53251 https://www.cve.org/CVERecord?id=CVE-2026-53251 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53253 https://www.cve.org/CVERecord?id=CVE-2026-53253 Référence CVE CVE-2026-53254 https://www.cve.org/CVERecord?id=CVE-2026-53254 Référence CVE CVE-2026-53255 https://www.cve.org/CVERecord?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53257 https://www.cve.org/CVERecord?id=CVE-2026-53257 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1253Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-23137 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43344 https://www.cve.org/CVERecord?id=CVE-2026-43344 Référence CVE CVE-2026-45963 https://www.cve.org/CVERecord?id=CVE-2026-45963 Référence CVE CVE-2026-52944 https://www.cve.org/CVERecord?id=CVE-2026-52944 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53089 https://www.cve.org/CVERecord?id=CVE-2026-53089 Référence CVE CVE-2026-53102 https://www.cve.org/CVERecord?id=CVE-2026-53102 Référence CVE CVE-2026-53113 https://www.cve.org/CVERecord?id=CVE-2026-53113 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53313 https://www.cve.org/CVERecord?id=CVE-2026-53313 Référence CVE CVE-2026-64058 https://www.cve.org/CVERecord?id=CVE-2026-64058 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64210 https://www.cve.org/CVERecord?id=CVE-2026-64210 Référence CVE CVE-2026-68286 https://www.cve.org/CVERecord?id=CVE-2026-68286 Référence CVE CVE-2026-68287 https://www.cve.org/CVERecord?id=CVE-2026-68287 Référence CVE CVE-2026-68288 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53243 https://www.cve.org/CVERecord?id=CVE-2026-53243 Référence CVE CVE-2026-53244 https://www.cve.org/CVERecord?id=CVE-2026-53244 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53247 https://www.cve.org/CVERecord?id=CVE-2026-53247 Référence CVE CVE-2026-53248 https://www.cve.org/CVERecord?id=CVE-2026-53248 Référence CVE CVE-2026-53249 https://www.cve.org/CVERecord?id=CVE-2026-53249 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53251 https://www.cve.org/CVERecord?id=CVE-2026-53251 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53253 https://www.cve.org/CVERecord?id=CVE-2026-53253 Référence CVE CVE-2026-53254 https://www.cve.org/CVERecord?id=CVE-2026-53254 Référence CVE CVE-2026-53255 https://www.cve.org/CVERecord?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53257 https://www.cve.org/CVERecord?id=CVE-2026-53257 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53240 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53243 https://www.cve.org/CVERecord?id=CVE-2026-53243 Référence CVE CVE-2026-53244 https://www.cve.org/CVERecord?id=CVE-2026-53244 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53248 https://www.cve.org/CVERecord?id=CVE-2026-53248 Référence CVE CVE-2026-53249 https://www.cve.org/CVERecord?id=CVE-2026-53249 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53251 https://www.cve.org/CVERecord?id=CVE-2026-53251 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53253 https://www.cve.org/CVERecord?id=CVE-2026-53253 Référence CVE CVE-2026-53254 https://www.cve.org/CVERecord?id=CVE-2026-53254 Référence CVE CVE-2026-53255 https://www.cve.org/CVERecord?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53257 https://www.cve.org/CVERecord?id=CVE-2026-53257 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53243 https://www.cve.org/CVERecord?id=CVE-2026-53243 Référence CVE CVE-2026-53244 https://www.cve.org/CVERecord?id=CVE-2026-53244 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53247 https://www.cve.org/CVERecord?id=CVE-2026-53247 Référence CVE CVE-2026-53248 https://www.cve.org/CVERecord?id=CVE-2026-53248 Référence CVE CVE-2026-53249 https://www.cve.org/CVERecord?id=CVE-2026-53249 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53251 https://www.cve.org/CVERecord?id=CVE-2026-53251 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53253 https://www.cve.org/CVERecord?id=CVE-2026-53253 Référence CVE CVE-2026-53254 https://www.cve.org/CVERecord?id=CVE-2026-53254 Référence CVE CVE-2026-53255 https://www.cve.org/CVERecord?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53257 https://www.cve.org/CVERecord?id=CVE-2026-53257 Référence CVE CVE-2026-53258 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53185 Référence CVE CVE-2026-53189 https://www.cve.org/CVERecord?id=CVE-2026-53189 Référence CVE CVE-2026-53196 https://www.cve.org/CVERecord?id=CVE-2026-53196 Référence CVE CVE-2026-53212 https://www.cve.org/CVERecord?id=CVE-2026-53212 Référence CVE CVE-2026-53221 https://www.cve.org/CVERecord?id=CVE-2026-53221 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53230 https://www.cve.org/CVERecord?id=CVE-2026-53230 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53262 https://www.cve.org/CVERecord?id=CVE-2026-53262 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=CVE-2026-53265 Référence CVE CVE-2026-53267 https://www.cve.org/CVERecord?id=CVE-2026-53267 Référence CVE CVE-2026-53270 https://www.cve.org/CVERecord?id=CVE-2026-53270 Référence CVE CVE-2026-53275 https://www.cve.org/CVERecord?id=CVE-2026-53275 Référence CVE CVE-2026-53289 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53235 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53237 https://www.cve.org/CVERecord?id=CVE-2026-53237 Référence CVE CVE-2026-53239 https://www.cve.org/CVERecord?id=CVE-2026-53239 Référence CVE CVE-2026-53241 https://www.cve.org/CVERecord?id=CVE-2026-53241 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53247 https://www.cve.org/CVERecord?id=CVE-2026-53247 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53251 https://www.cve.org/CVERecord?id=CVE-2026-53251 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53253 https://www.cve.org/CVERecord?id=CVE-2026-53253 Référence CVE CVE-2026-53254 https://www.cve.org/CVERecord?id=CVE-2026-53254 Référence CVE CVE-2026-53255 https://www.cve.org/CVERecord?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53265 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1029Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53218 Référence CVE CVE-2026-53224 https://www.cve.org/CVERecord?id=CVE-2026-53224 Référence CVE CVE-2026-53225 https://www.cve.org/CVERecord?id=CVE-2026-53225 Référence CVE CVE-2026-53227 https://www.cve.org/CVERecord?id=CVE-2026-53227 Référence CVE CVE-2026-53236 https://www.cve.org/CVERecord?id=CVE-2026-53236 Référence CVE CVE-2026-53242 https://www.cve.org/CVERecord?id=CVE-2026-53242 Référence CVE CVE-2026-53245 https://www.cve.org/CVERecord?id=CVE-2026-53245 Référence CVE CVE-2026-53246 https://www.cve.org/CVERecord?id=CVE-2026-53246 Référence CVE CVE-2026-53249 https://www.cve.org/CVERecord?id=CVE-2026-53249 Référence CVE CVE-2026-53250 https://www.cve.org/CVERecord?id=CVE-2026-53250 Référence CVE CVE-2026-53252 https://www.cve.org/CVERecord?id=CVE-2026-53252 Référence CVE CVE-2026-53254 https://www.cve.org/CVERecord?id=CVE-2026-53254 Référence CVE CVE-2026-53255 https://www.cve.org/CVERecord?id=CVE-2026-53255 Référence CVE CVE-2026-53256 https://www.cve.org/CVERecord?id=CVE-2026-53256 Référence CVE CVE-2026-53260 https://www.cve.org/CVERecord?id=CVE-2026-53260 Référence CVE CVE-2026-53262 https://www.cve.org/CVERecord?id=CVE-2026-53262 Référence CVE CVE-2026-53267 https://www.cve.org/CVERecord?id=CVE-2026-53267 Référence CVE CVE-2026-53268 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023052LinuxのLinux KernelにおけるTime-of-check Time-of-use (TOCTOU) 競合状態の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。xsk: xsk_skb_metadata()内のTOCTOU問題を修正するために、csum_startとcsum_offsetをキャッシュするようにしました。TXメタデータ領域はUMEMバッファ内にあり、このバッファはメモリマップされており、ユーザースペースから同時に書き込みが可能です。xsk_skb_metadata()関数では、範囲チェックのために共有メモリからcsum_startとcsum_offsetを読み込み、その後skb割り当てのために再度読み込みます。悪意あるユーザースペースのアプリケーションは、これら2回の読み込みの間に値を書き換える競合（レースコンディション）を発生させて範囲チェックを回避し、送信パスでのチェックサム計算中に境界外メモリアクセスを引き起こす可能性があります。この問題は、csum_startとcsum_offsetを一度ローカル変数に読み込み、そのローカルコピーを検証と割り当ての両方で使用することで修正しました。その他のメタデータフィールド（flags、launch_time）やキャッシュされたcsumフィールドは、ユーザースペースによる同時書き込みのために相互に矛盾する可能性がありますが、これは無害です。唯一のセキュリティ上重要な不変条件は、検証された各フィールドの値が実際に使用される値と一致することであり、ローカルキャッシュによってこれが保証されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.8, 6.12.110 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 25 Jun 2026 · Last source change 14 Sept 2026, 11:58 UTC · CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-39201
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    48eb03dd26304c24f03bdbb9382e89c8564e71df < 0dfe05b938435892875e07771170051346412df9; 48eb03dd26304c24f03bdbb9382e89c8564e71df < bfdfd2706d5fb2cd496a1506e680daf979309c8b; 48eb03dd26304c24f03bdbb9382e89c8564e71df < 22ba97ea9cc1f63a0d0244fae38057ed452b6ac7; 6.8 · Fixed: < 6.8; 6.18.36 ≤ 6.18.*; 7.0.13 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: 48eb03dd26304c24f03bdbb9382e89c8564e71df < eb778aed8a9b2381668fcb1247ae4fa011224768, 48eb03dd26304c24f03bdbb9382e89c8564e71df < 0dfe05b938435892875e07771170051346412df9, 48eb03dd26304c24f03bdbb9382e89c8564e71df < bfdfd2706d5fb2cd496a1506e680daf979309c8b, 48eb03dd26304c24f03bdbb9382e89c8564e71df < 22ba97ea9cc1f63a0d0244fae38057ed452b6ac7, 6.8 · Fixed: Linux: < 6.8, 6.12.110 ≤ 6.12.*, 6.18.36 ≤ 6.18.*, 7.0.13 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-39201↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-53250 · cve.blacktree.nl