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

xfrm: prevent policy_hthresh.work from racing with netns teardown

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 21 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.14% 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 21 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 21 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 · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 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 6 Oct 2026
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-24900

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
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 21 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: xfrm: prevent policy_hthresh.work from racing with netns teardown A XFRM_MSG_NEWSPDINFO request can queue the per-net work item policy_hthresh.work onto the system workqueue. The queued callback, xfrm_hash_rebuild(), retrieves the enclosing struct net via container_of(). If the net namespace is torn down before that work runs, the associated struct net may already have been freed, and xfrm_hash_rebuild() may then dereference stale memory. xfrm_policy_fini() already flushes policy_hash_work during teardown, but it does not synchronize policy_hthresh.work. Synchronize policy_hthresh.work in xfrm_policy_fini() as well, so the queued work cannot outlive the net namespace teardown and access a freed struct net.

What

In the Linux kernel, the following vulnerability has been resolved: xfrm: prevent policy_hthresh.work from racing with netns teardown A XFRM_MSG_NEWSPDINFO request can queue the per-net work item policy_hthresh.work onto the system workqueue. The queued callback, xfrm_hash_rebuild(), retrieves the enclosing struct net via container_of(). If the net namespace is torn down before that work runs, the associated struct net may already have been freed, and xfrm_hash_rebuild() may then dereference stale memory. xfrm_policy_fini() already flushes policy_hash_work during teardown, but it does not synchronize policy_hthresh.work. Synchronize policy_hthresh.work in xfrm_policy_fini() as well, so the queued work cannot outlive the net namespace teardown and access a freed struct net.

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: xfrm: prevent policy_hthresh.work from racing with netns teardown A XFRM_MSG_NEWSPDINFO request can queue the per-net work item policy_hthresh.work onto the system workqueue. The queued callback, xfrm_hash_rebuild(), retrieves the enclosing struct net via container_of(). If the net namespace is torn down before that work runs, the associated struct net may already have been freed, and xfrm_hash_rebuild() may then dereference stale memory. xfrm_policy_fini() already flushes policy_hash_work during teardown, but it does not synchronize policy_hthresh.work. Synchronize policy_hthresh.work in xfrm_policy_fini() as well, so the queued work cannot outlive the net namespace teardown and access a freed struct net.

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.

BSI · German · WID-SEC-2026-1252Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 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-31503 Référence CVE CVE-2026-31505 https://www.cve.org/CVERecord?id=CVE-2026-31505 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31525 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-31505 Référence CVE CVE-2026-31506 https://www.cve.org/CVERecord?id=CVE-2026-31506 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31525 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-31505 Référence CVE CVE-2026-31506 https://www.cve.org/CVERecord?id=CVE-2026-31506 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31525 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-31480 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31493 https://www.cve.org/CVERecord?id=CVE-2026-31493 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=CVE-2026-3150 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31493 https://www.cve.org/CVERecord?id=CVE-2026-31493 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=CVE-2026-3150 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31554 https://www.cve.org/CVERecord?id=CVE-2026-31554 Référence CVE CVE-2026-31555 https://www.cve.org/CVERecord?id=CVE-2026-31555 Référence CVE CVE-2026-31560 https://www.cve.org/CVERecord?id=CVE-2026-31560 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31592 https://www.cve.org/CVERecord?id=CVE-2026-31592 Référence CVE CVE-2026-31593 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31493 https://www.cve.org/CVERecord?id=CVE-2026-31493 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=CVE-2026-3150 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31590 https://www.cve.org/CVERecord?id=CVE-2026-31590 Référence CVE CVE-2026-31591 https://www.cve.org/CVERecord?id=CVE-2026-31591 Référence CVE CVE-2026-31596 https://www.cve.org/CVERecord?id=CVE-2026-31596 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31614 https://www.cve.org/CVERecord?id=CVE-2026-31614 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31493 https://www.cve.org/CVERecord?id=CVE-2026-31493 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=CVE-2026-3150 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31540 https://www.cve.org/CVERecord?id=CVE-2026-31540 Référence CVE CVE-2026-31546 https://www.cve.org/CVERecord?id=CVE-2026-31546 Référence CVE CVE-2026-31556 https://www.cve.org/CVERecord?id=CVE-2026-31556 Référence CVE CVE-2026-31562 https://www.cve.org/CVERecord?id=CVE-2026-31562 Référence CVE CVE-2026-31568 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31406 https://www.cve.org/CVERecord?id=CVE-2026-31406 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31493 https://www.cve.org/CVERecord?id=CVE-2026-31493 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=CVE-2026-3150 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31568 https://www.cve.org/CVERecord?id=CVE-2026-31568 Référence CVE CVE-2026-31575 https://www.cve.org/CVERecord?id=CVE-2026-31575 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31614 https://www.cve.org/CVERecord?id=CVE-2026-31614 Référence CVE CVE-2026-31629 https://www.cve.org/CVERecord?id=CVE-2026-31629 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31505 Référence CVE CVE-2026-31506 https://www.cve.org/CVERecord?id=CVE-2026-31506 Référence CVE CVE-2026-31507 https://www.cve.org/CVERecord?id=CVE-2026-31507 Référence CVE CVE-2026-31508 https://www.cve.org/CVERecord?id=CVE-2026-31508 Référence CVE CVE-2026-31509 https://www.cve.org/CVERecord?id=CVE-2026-31509 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31511 https://www.cve.org/CVERecord?id=CVE-2026-31511 Référence CVE CVE-2026-31512 https://www.cve.org/CVERecord?id=CVE-2026-31512 Référence CVE CVE-2026-31515 https://www.cve.org/CVERecord?id=CVE-2026-31515 Référence CVE CVE-2026-31516 https://www.cve.org/CVERecord?id=CVE-2026-31516 Référence CVE CVE-2026-31518 https://www.cve.org/CVERecord?id=CVE-2026-31518 Référence CVE CVE-2026-31519 https://www.cve.org/CVERecord?id=CVE-2026-31519 Référence CVE CVE-2026-31520 https://www.cve.org/CVERecord?id=CVE-2026-31520 Référence CVE CVE-2026-31521 https://www.cve.org/CVERecord?id=CVE-2026-31521 Référence CVE CVE-2026-31522 https://www.cve.org/CVERecord?id=CVE-2026-31522 Référence CVE CVE-2026-31523 https://www.cve.org/CVERecord?id=CVE-2026-31523 Référence CVE CVE-2026-31524 https://www.cve.org/CVERecord?id=CVE-2026-31524 Référence CVE CVE-2026-31525 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。xfrm: policy_hthresh.workがnetnsの破棄と競合しないように防止します。XFRM_MSG_NEWSPDINFOリクエストは、システムワークキュー上にネットワークごとの作業項目であるpolicy_hthresh.workをキューイングできます。キューに入ったコールバックであるxfrm_hash_rebuild()はcontainer_of()を使って囲むstruct netを取得します。しかし、ネットワーク名前空間がその作業が実行される前に破棄されると、関連するstruct netはすでに解放されている可能性があり、xfrm_hash_rebuild()が古いメモリを参照してしまうことがあります。xfrm_policy_fini()は破棄中にpolicy_hash_workをすでにフラッシュしていますが、policy_hthresh.workは同期していません。そのため、xfrm_policy_fini()内でもpolicy_hthresh.workを同期させることで、キューイングされた作業がネットワーク名前空間の破棄より長く残り、解放済みのstruct netへのアクセスを防止します。

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
Linux: 880a6fab8f6ba5b5abe59ea68533202ddea1012c < 56ea2257b83ee29a543f158159e3d1abc1e3e4fe, 880a6fab8f6ba5b5abe59ea68533202ddea1012c < 8854e9367465d784046362698731c1111e3b39b8, 880a6fab8f6ba5b5abe59ea68533202ddea1012c < 4e2e77843fef473ef47e322d52436d8308582a96, 880a6fab8f6ba5b5abe59ea68533202ddea1012c < 29fe3a61bcdce398ee3955101c39f89c01a8a77e, 3.18
Fixed
Linux: < 3.18, 6.12.80 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
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 22 Apr 2026 · Last source change 5 Aug 2026, 12:23 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-24900
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-31516 · cve.blacktree.nl