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

net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd()

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

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 25 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 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.15% 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 25 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.

24 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.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.3-1Debian Security Tracker ↗Source updated 6 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
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via __packet_snd_vnet_parse() but then re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent userspace thread can modify the vnet_hdr fields between validation and use, bypassing all safety checks. The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr to a stack-local variable. All other vnet_hdr consumers in the kernel (tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX path is the only caller of virtio_net_hdr_to_skb() that reads directly from user-controlled shared memory. Fix this by copying vnet_hdr from the mmap'd ring buffer to a stack-local variable before validation and use, consistent with the approach used in packet_snd() and all other callers.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-26509

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via __packet_snd_vnet_parse() but then re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent userspace thread can modify the vnet_hdr fields between validation and use, bypassing all safety checks. The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr to a stack-local variable. All other vnet_hdr consumers in the kernel (tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX path is the only caller of virtio_net_hdr_to_skb() that reads directly from user-controlled shared memory. Fix this by copying vnet_hdr from the mmap'd ring buffer to a stack-local variable before validation and use, consistent with the approach used in packet_snd() and all other callers.

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 25 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: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via __packet_snd_vnet_parse() but then re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent userspace thread can modify the vnet_hdr fields between validation and use, bypassing all safety checks. The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr to a stack-local variable. All other vnet_hdr consumers in the kernel (tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX path is the only caller of virtio_net_hdr_to_skb() that reads directly from user-controlled shared memory. Fix this by copying vnet_hdr from the mmap'd ring buffer to a stack-local variable before validation and use, consistent with the approach used in packet_snd() and all other callers.

What

In the Linux kernel, the following vulnerability has been resolved: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via __packet_snd_vnet_parse() but then re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent userspace thread can modify the vnet_hdr fields between validation and use, bypassing all safety checks. The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr to a stack-local variable. All other vnet_hdr consumers in the kernel (tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX path is the only caller of virtio_net_hdr_to_skb() that reads directly from user-controlled shared memory. Fix this by copying vnet_hdr from the mmap'd ring buffer to a stack-local variable before validation and use, consistent with the approach used in packet_snd() and all other callers.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via __packet_snd_vnet_parse() but then re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent userspace thread can modify the vnet_hdr fields between validation and use, bypassing all safety checks. The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr to a stack-local variable. All other vnet_hdr consumers in the kernel (tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX path is the only caller of virtio_net_hdr_to_skb() that reads directly from user-controlled shared memory. Fix this by copying vnet_hdr from the mmap'd ring buffer to a stack-local variable before validation and use, consistent with the approach used in packet_snd() and all other callers.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('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-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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-362
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-26509Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net/packet: fix TOCTOU race on mmap'd vnet_hdr in tpacket_snd() In tpacket_snd(), when PACKET_VNET_HDR is enabled, vnet_hdr points directly into the mmap'd TX ring buffer shared with userspace. The kernel validates the header via __packet_snd_vnet_parse() but then re-reads all fields later in virtio_net_hdr_to_skb(). A concurrent userspace thread can modify the vnet_hdr fields between validation and use, bypassing all safety checks. The non-TPACKET path (packet_snd()) already correctly copies vnet_hdr to a stack-local variable. All other vnet_hdr consumers in the kernel (tun.c, tap.c, virtio_net.c) also use stack copies. The TPACKET TX path is the only caller of virtio_net_hdr_to_skb() that reads directly from user-controlled shared memory. Fix this by copying vnet_hdr from the mmap'd ring buffer to a stack-local variable before validation and use, consistent with the approach used in packet_snd() and all other callers.

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

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

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

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

d?id=CVE-2026-31684 Référence CVE CVE-2026-31686 https://www.cve.org/CVERecord?id=CVE-2026-31686 Référence CVE CVE-2026-31689 https://www.cve.org/CVERecord?id=CVE-2026-31689 Référence CVE CVE-2026-31694 https://www.cve.org/CVERecord?id=CVE-2026-31694 Référence CVE CVE-2026-31695 https://www.cve.org/CVERecord?id=CVE-2026-31695 Référence CVE CVE-2026-31696 https://www.cve.org/CVERecord?id=CVE-2026-31696 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=CVE-2026-31699 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31701 https://www.cve.org/CVERecord?id=CVE-2026-31701 Référence CVE CVE-2026-31702 https://www.cve.org/CVERecord?id=CVE-2026-31702 Référence CVE CVE-2026-31704 https://www.cve.org/CVERecord?id=CVE-2026-31704 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-31706 https://www.cve.org/CVERecord?id=CVE-2026-31706 Référence CVE CVE-2026-31707 https://www.cve.org/CVERecord?id=CVE-2026-31707 Référence CVE CVE-2026-31708 https://www.cve.org/CVERecord?id=CVE-2026-31708 Référence CVE CVE-2026-31709 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31687 Référence CVE CVE-2026-31689 https://www.cve.org/CVERecord?id=CVE-2026-31689 Référence CVE CVE-2026-31693 https://www.cve.org/CVERecord?id=CVE-2026-31693 Référence CVE CVE-2026-31694 https://www.cve.org/CVERecord?id=CVE-2026-31694 Référence CVE CVE-2026-31695 https://www.cve.org/CVERecord?id=CVE-2026-31695 Référence CVE CVE-2026-31696 https://www.cve.org/CVERecord?id=CVE-2026-31696 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=CVE-2026-31699 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31701 https://www.cve.org/CVERecord?id=CVE-2026-31701 Référence CVE CVE-2026-31702 https://www.cve.org/CVERecord?id=CVE-2026-31702 Référence CVE CVE-2026-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31704 https://www.cve.org/CVERecord?id=CVE-2026-31704 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-31706 https://www.cve.org/CVERecord?id=CVE-2026-31706 Référence CVE CVE-2026-31707 https://www.cve.org/CVERecord?id=CVE-2026-31707 Référence CVE CVE-2026-31708 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31686 Référence CVE CVE-2026-31687 https://www.cve.org/CVERecord?id=CVE-2026-31687 Référence CVE CVE-2026-31689 https://www.cve.org/CVERecord?id=CVE-2026-31689 Référence CVE CVE-2026-31694 https://www.cve.org/CVERecord?id=CVE-2026-31694 Référence CVE CVE-2026-31695 https://www.cve.org/CVERecord?id=CVE-2026-31695 Référence CVE CVE-2026-31696 https://www.cve.org/CVERecord?id=CVE-2026-31696 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=CVE-2026-31699 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31701 https://www.cve.org/CVERecord?id=CVE-2026-31701 Référence CVE CVE-2026-31702 https://www.cve.org/CVERecord?id=CVE-2026-31702 Référence CVE CVE-2026-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31704 https://www.cve.org/CVERecord?id=CVE-2026-31704 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-31706 https://www.cve.org/CVERecord?id=CVE-2026-31706 Référence CVE CVE-2026-31707 https://www.cve.org/CVERecord?id=CVE-2026-31707 Référence CVE CVE-2026-31708 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31676 Référence CVE CVE-2026-31681 https://www.cve.org/CVERecord?id=CVE-2026-31681 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31686 https://www.cve.org/CVERecord?id=CVE-2026-31686 Référence CVE CVE-2026-31696 https://www.cve.org/CVERecord?id=CVE-2026-31696 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=CVE-2026-31699 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31701 https://www.cve.org/CVERecord?id=CVE-2026-31701 Référence CVE CVE-2026-31702 https://www.cve.org/CVERecord?id=CVE-2026-31702 Référence CVE CVE-2026-31704 https://www.cve.org/CVERecord?id=CVE-2026-31704 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-31708 https://www.cve.org/CVERecord?id=CVE-2026-31708 Référence CVE CVE-2026-31709 https://www.cve.org/CVERecord?id=CVE-2026-31709 Référence CVE CVE-2026-31711 https://www.cve.org/CVERecord?id=CVE-2026-31711 Référence CVE CVE-2026-31712 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31685 Référence CVE CVE-2026-31686 https://www.cve.org/CVERecord?id=CVE-2026-31686 Référence CVE CVE-2026-31687 https://www.cve.org/CVERecord?id=CVE-2026-31687 Référence CVE CVE-2026-31693 https://www.cve.org/CVERecord?id=CVE-2026-31693 Référence CVE CVE-2026-31694 https://www.cve.org/CVERecord?id=CVE-2026-31694 Référence CVE CVE-2026-31696 https://www.cve.org/CVERecord?id=CVE-2026-31696 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=CVE-2026-31699 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31701 https://www.cve.org/CVERecord?id=CVE-2026-31701 Référence CVE CVE-2026-31702 https://www.cve.org/CVERecord?id=CVE-2026-31702 Référence CVE CVE-2026-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31704 https://www.cve.org/CVERecord?id=CVE-2026-31704 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-31706 https://www.cve.org/CVERecord?id=CVE-2026-31706 Référence CVE CVE-2026-31707 https://www.cve.org/CVERecord?id=CVE-2026-31707 Référence CVE CVE-2026-31708 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31685 Référence CVE CVE-2026-31686 https://www.cve.org/CVERecord?id=CVE-2026-31686 Référence CVE CVE-2026-31687 https://www.cve.org/CVERecord?id=CVE-2026-31687 Référence CVE CVE-2026-31693 https://www.cve.org/CVERecord?id=CVE-2026-31693 Référence CVE CVE-2026-31694 https://www.cve.org/CVERecord?id=CVE-2026-31694 Référence CVE CVE-2026-31696 https://www.cve.org/CVERecord?id=CVE-2026-31696 Référence CVE CVE-2026-31697 https://www.cve.org/CVERecord?id=CVE-2026-31697 Référence CVE CVE-2026-31698 https://www.cve.org/CVERecord?id=CVE-2026-31698 Référence CVE CVE-2026-31699 https://www.cve.org/CVERecord?id=CVE-2026-31699 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31701 https://www.cve.org/CVERecord?id=CVE-2026-31701 Référence CVE CVE-2026-31702 https://www.cve.org/CVERecord?id=CVE-2026-31702 Référence CVE CVE-2026-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31704 https://www.cve.org/CVERecord?id=CVE-2026-31704 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-31706 https://www.cve.org/CVERecord?id=CVE-2026-31706 Référence CVE CVE-2026-31707 https://www.cve.org/CVERecord?id=CVE-2026-31707 Référence CVE CVE-2026-31708 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31675 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31679 https://www.cve.org/CVERecord?id=CVE-2026-31679 Référence CVE CVE-2026-31681 https://www.cve.org/CVERecord?id=CVE-2026-31681 Référence CVE CVE-2026-31682 https://www.cve.org/CVERecord?id=CVE-2026-31682 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31691 https://www.cve.org/CVERecord?id=CVE-2026-31691 Référence CVE CVE-2026-31694 https://www.cve.org/CVERecord?id=CVE-2026-31694 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43009 https://www.cve.org/CVERecord?id=CVE-2026-43009 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43044 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31512 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31602 https://www.cve.org/CVERecord?id=CVE-2026-31602 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=CVE-2026-31649 Référence CVE CVE-2026-31667 https://www.cve.org/CVERecord?id=CVE-2026-31667 Référence CVE CVE-2026-31675 https://www.cve.org/CVERecord?id=CVE-2026-31675 Référence CVE CVE-2026-31681 https://www.cve.org/CVERecord?id=CVE-2026-31681 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31700 https://www.cve.org/CVERecord?id=CVE-2026-31700 Référence CVE CVE-2026-31738 https://www.cve.org/CVERecord?id=CVE-2026-31738 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43025 https://www.cve.org/CVERecord?id=CVE-2026-43025 Référence CVE CVE-2026-43088 https://www.cve.org/CVERecord?id=CVE-2026-43088 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43126 https://www.cve.org/CVERecord?id=CVE-2026-43126 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43255 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0526Multiples vulnérabilités dans les produits Microsoft

Bulletin de sécurité Microsoft CVE-2026-31648 du 29 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31661 du 29 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31689 du 29 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31508 du 30 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31533 du 01 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31694 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31696 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31697 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31698 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31699 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31700 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31702 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31704 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31705 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31708 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31711 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-31721 du 02 mai 2026 Bulletin de sécurité Microsoft CVE-2026-43033 du 02 mai 2026 Une gestion de version détaillée se trouve à la fin de ce document. Risque Non spécifié par l'éditeur Systèmes affectés azl3 kernel versions antérieures à 6.6.137.1-1 Résumé De multiples vulnérabilités ont é

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014370LinuxのLinux Kernelにおける競合状態に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました：net/packetのtpacket_snd()内でmmapされたvnet_hdrに対するTOCTOU競合状態を修正しました。tpacket_snd()では、PACKET_VNET_HDRが有効な場合、vnet_hdrはユーザースペースと共有されるmmapされたTXリングバッファを直接指します。カーネルは__packet_snd_vnet_parse()でヘッダーを検証しますが、その後virtio_net_hdr_to_skb()で全フィールドを再読み込みします。この間にユーザースペースのスレッドがvnet_hdrフィールドを変更すると、安全性チェックをすり抜ける可能性があります。非TPACKETパス（packet_snd()）では既にvnet_hdrをスタックローカル変数に正しくコピーしています。カーネル内の他のvnet_hdrの利用箇所（tun.c、tap.c、virtio_net.c）もスタックコピーを使用しています。TPACKET TXパスのみがvirtio_net_hdr_to_skb()を呼び出し、ユーザー制御の共有メモリから直接読み取っていました。この問題は、packet_snd()や他の呼び出し元と同様に、検証および使用前にmmapされたリングバッファからvnet_hdrをスタックローカル変数にコピーする方法で修正されました。

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: < 4.6, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.136 ≤ 6.6.*, 6.12.84 ≤ 6.12.*, 6.18.25 ≤ 6.18.*, 7.0.2 ≤ 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
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 1 May 2026 · Last source change 8 Sept 2026, 08:48 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('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-26509
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
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
    1d036d25e5609ba73fee6a88db01c306b140d512 < 0f4c9754956b86de158a4af5278c5cf5bda9439e; 1d036d25e5609ba73fee6a88db01c306b140d512 < 714aa973da8163925eda7efd49361ccbee21ee46; 1d036d25e5609ba73fee6a88db01c306b140d512 < 1490f82353bdabc09265a74e645b07f05cf4188e; 1d036d25e5609ba73fee6a88db01c306b140d512 < 74e2db36fe50e3ad9d5300d7fd0e6e2a15a6d121; 1d036d25e5609ba73fee6a88db01c306b140d512 < 3a1bf9116ea31470b89692585c3910dfe830dcdd; 1d036d25e5609ba73fee6a88db01c306b140d512 < 28324a3b62d9ce7f9bdd65a8ce63f382041d1b27; 1d036d25e5609ba73fee6a88db01c306b140d512 < 48a6ef291a17639e1b6ae0fbe9c8b2bb87d7804b; 1d036d25e5609ba73fee6a88db01c306b140d512 < 2c054e17d9d41f1020376806c7f750834ced4dc5 · Fixed: < 4.6; 5.10.259 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.176 ≤ 6.1.*; 6.6.136 ≤ 6.6.*; 6.12.84 ≤ 6.12.*; 6.18.25 ≤ 6.18.*; 7.0.2 ≤ 7.0.*
    After
    Linux: 1d036d25e5609ba73fee6a88db01c306b140d512 < 0f4c9754956b86de158a4af5278c5cf5bda9439e, 1d036d25e5609ba73fee6a88db01c306b140d512 < 714aa973da8163925eda7efd49361ccbee21ee46, 1d036d25e5609ba73fee6a88db01c306b140d512 < 1490f82353bdabc09265a74e645b07f05cf4188e, 1d036d25e5609ba73fee6a88db01c306b140d512 < 74e2db36fe50e3ad9d5300d7fd0e6e2a15a6d121, 1d036d25e5609ba73fee6a88db01c306b140d512 < 3a1bf9116ea31470b89692585c3910dfe830dcdd, 1d036d25e5609ba73fee6a88db01c306b140d512 < 28324a3b62d9ce7f9bdd65a8ce63f382041d1b27, 1d036d25e5609ba73fee6a88db01c306b140d512 < 48a6ef291a17639e1b6ae0fbe9c8b2bb87d7804b, 1d036d25e5609ba73fee6a88db01c306b140d512 < 2c054e17d9d41f1020376806c7f750834ced4dc5, 4.6 · Fixed: Linux: < 4.6, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.176 ≤ 6.1.*, 6.6.136 ≤ 6.6.*, 6.12.84 ≤ 6.12.*, 6.18.25 ≤ 6.18.*, 7.0.2 ≤ 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-26509↗Vendor CSAF · Siemens ProductCERT · Siemens SSA-019113↗Patch or update reference↗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-31700 · cve.blacktree.nl