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

writeback: Fix use after free in inode_switch_wbs_work_fn()

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 11 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 20 Aug 2026

Evidence used

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

15 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 11 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 · 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 · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-oracle-6.14Affected, 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
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-31703 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: writeback: Fix use after free in inode_switch_wbs_work_fn()
274 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel. A use-after-free vulnerability exists in the `inode_switch_wbs_work_fn()` function, part of the kernel's writeback subsystem. This issue arises when a work item remains active after its associated memory object (`wb`) has been released, leading to system instability. An attacker could potentially exploit this vulnerability to cause a denial of service.
Remediation
No remediation text is recorded.
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-26512

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: writeback: Fix use after free in inode_switch_wbs_work_fn() inode_switch_wbs_work_fn() has a loop like: wb_get(new_wb); while (1) { list = llist_del_all(&new_wb->switch_wbs_ctxs); /* Nothing to do? */ if (!list) break; ... process the items ... } Now adding of items to the list looks like: wb_queue_isw() if (llist_add(&isw->list, &wb->switch_wbs_ctxs)) queue_work(isw_wq, &wb->switch_work); Because inode_switch_wbs_work_fn() loops when processing isw items, it can happen that wb->switch_work is pending while wb->switch_wbs_ctxs is empty. This is a problem because in that case wb can get freed (no isw items -> no wb reference) while the work is still pending causing use-after-free issues. We cannot just fix this by cancelling work when freeing wb because that could still trigger problematic 0 -> 1 transitions on wb refcount due to wb_get() in inode_switch_wbs_work_fn(). It could be all handled with more careful code but that seems unnecessarily complex so let's avoid that until it is proven that the looping actually brings practical benefit. Just remove the loop from inode_switch_wbs_work_fn() instead. That way when wb_queue_isw() queues work, we are guaranteed we have added the first item to wb->switch_wbs_ctxs and nobody is going to remove it (and drop the wb reference it holds) until the queued work runs.

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 11 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: writeback: Fix use after free in inode_switch_wbs_work_fn() inode_switch_wbs_work_fn() has a loop like: wb_get(new_wb); while (1) { list = llist_del_all(&new_wb->switch_wbs_ctxs); /* Nothing to do? */ if (!list) break; ... process the items ... } Now adding of items to the list looks like: wb_queue_isw() if (llist_add(&isw->list, &wb->switch_wbs_ctxs)) queue_work(isw_wq, &wb->switch_work); Because inode_switch_wbs_work_fn() loops when processing isw items, it can happen that wb->switch_work is pending while wb->switch_wbs_ctxs is empty. This is a problem because in that case wb can get freed (no isw items -> no wb reference) while the work is still pending causing use-after-free issues. We cannot just fix this by cancelling work when freeing wb because that could still trigger problematic 0 -> 1 transitions on wb refcount due to wb_get() in inode_switch_wbs_work_fn(). It could be all handled with more careful code but that seems unnecessarily complex so let's avoid that until it is proven that the looping actually brings practical benefit. Just remove the loop from inode_switch_wbs_work_fn() instead. That way when wb_queue_isw() queues work, we are guaranteed we have added the first item to wb->switch_wbs_ctxs and nobody is going to remove it (and drop the wb reference it holds) until the queued work runs.

What

In the Linux kernel, the following vulnerability has been resolved: writeback: Fix use after free in inode_switch_wbs_work_fn() inode_switch_wbs_work_fn() has a loop like: wb_get(new_wb); while (1) { list = llist_del_all(&new_wb->switch_wbs_ctxs); /* Nothing to do? */ if (!list) break; ... process the items ... } Now adding of items to the list looks like: wb_queue_isw() if (llist_add(&isw->list, &wb->switch_wbs_ctxs)) queue_work(isw_wq, &wb->switch_work); Because inode_switch_wbs_work_fn() loops when processing isw items, it can happen that wb->switch_work is pending while wb->switch_wbs_ctxs is empty. This is a problem because in that case wb can get freed (no isw items -> no wb reference) while the work is still pending causing use-after-free issues. We cannot just fix this by cancelling work when freeing wb because that could still trigger problematic 0 -> 1 transitions on wb refcount due to wb_get() in inode_switch_wbs_work_fn(). It could be all handled with more careful code but that seems unnecessarily complex so let's avoid that until it is proven that the looping actually brings practical benefit. Just remove the loop from inode_switch_wbs_work_fn() instead. That way when wb_queue_isw() queues work, we are guaranteed we have added the first item to wb->switch_wbs_ctxs and nobody is going to remove it (and drop the wb reference it holds) until the queued work runs.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

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: writeback: Fix use after free in inode_switch_wbs_work_fn() inode_switch_wbs_work_fn() has a loop like: wb_get(new_wb); while (1) { list = llist_del_all(&new_wb->switch_wbs_ctxs); /* Nothing to do? */ if (!list) break; ... process the items ... } Now adding of items to the list looks like: wb_queue_isw() if (llist_add(&isw->list, &wb->switch_wbs_ctxs)) queue_work(isw_wq, &wb->switch_work); Because inode_switch_wbs_work_fn() loops when processing isw items, it can happen that wb->switch_work is pending while wb->switch_wbs_ctxs is empty. This is a problem because in that case wb can get freed (no isw items -> no wb reference) while the work is still pending causing use-after-free issues. We cannot just fix this by cancelling work when freeing wb because that could still trigger problematic 0 -> 1 transitions on wb refcount due to wb_get() in inode_switch_wbs_work_fn(). It could be all handled with more careful code but that seems unnecessarily complex so let's avoid that until it is proven that the looping actually brings practical benefit. Just remove the loop from inode_switch_wbs_work_fn() instead. That way when wb_queue_isw() queues work, we are guaranteed we have added the first item to wb->switch_wbs_ctxs and nobody is going to remove it (and drop the wb reference it holds) until the queued work runs.

Why

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

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 → Expired Pointer Dereference → 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-825 ↗

CWE-825: Expired Pointer Dereference. The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-26512Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: writeback: Fix use after free in inode_switch_wbs_work_fn() inode_switch_wbs_work_fn() has a loop like: wb_get(new_wb); while (1) { list = llist_del_all(&new_wb->switch_wbs_ctxs); /* Nothing to do? */ if (!list) break; ... process the items ... } Now adding of items to the list looks like: wb_queue_isw() if (llist_add(&isw->list, &wb->switch_wbs_ctxs)) queue_work(isw_wq, &wb->switch_work); Because inode_switch_wbs_work_fn() loops when processing isw items, it can happen that wb->switch_work is pending while wb->switch_wbs_ctxs is empty. This is a problem because in that case wb can get freed (no isw items -> no wb reference) while the work is still pending causing use-after-free issues. We cannot just fix this by cancelling work when freeing wb because that could still trigger problematic 0 -> 1 transitions on wb refcount due to wb_get() in inode_switch_wbs_work_fn(). It could be all handled with more careful code but that seems unnecessarily complex so let's avoid that until it is proven that the looping actually brings practical benefit. Just remove the loop from inode_switch_wbs_work_fn() instead. That way when wb_queue_isw() queues work, we are guaranteed we have added the first item to wb->switch_wbs_ctxs and nobody is going to remove it (and drop the wb reference it holds) until the queued work runs.

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-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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=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-31710 https://www.cve.org/CVERecord?id=CVE-2026-31710 Référence CVE CVE-2026-31711 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-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=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-31710 https://www.cve.org/CVERecord?id=CVE-2026-31710 Référence CVE CVE-2026-31711 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31674 Référence CVE CVE-2026-31677 https://www.cve.org/CVERecord?id=CVE-2026-31677 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31680 https://www.cve.org/CVERecord?id=CVE-2026-31680 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-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-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31752 https://www.cve.org/CVERecord?id=CVE-2026-31752 Référence CVE CVE-2026-31758 https://www.cve.org/CVERecord?id=CVE-2026-31758 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-31767 https://www.cve.org/CVERecord?id=CVE-2026-31767 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-43010 https://www.cve.org/CVERecord?id=CVE-2026-43010 Référence CVE CVE-2026-43013 https://www.cve.org/CVERecord?id=CVE-2026-43013 Référence CVE CVE-2026-43022 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-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=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-31710 https://www.cve.org/CVERecord?id=CVE-2026-31710 Référence CVE CVE-2026-31711 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31680 https://www.cve.org/CVERecord?id=CVE-2026-31680 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-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-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31752 https://www.cve.org/CVERecord?id=CVE-2026-31752 Référence CVE CVE-2026-31758 https://www.cve.org/CVERecord?id=CVE-2026-31758 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-31767 https://www.cve.org/CVERecord?id=CVE-2026-31767 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-43013 https://www.cve.org/CVERecord?id=CVE-2026-43013 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43024 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-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=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-31710 https://www.cve.org/CVERecord?id=CVE-2026-31710 Référence CVE CVE-2026-31711 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31629 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31694 https://www.cve.org/CVERecord?id=CVE-2026-31694 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-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31758 https://www.cve.org/CVERecord?id=CVE-2026-31758 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-31767 https://www.cve.org/CVERecord?id=CVE-2026-31767 Référence CVE CVE-2026-31771 https://www.cve.org/CVERecord?id=CVE-2026-31771 Référence CVE CVE-2026-31774 https://www.cve.org/CVERecord?id=CVE-2026-31774 Référence CVE CVE-2026-43009 https://www.cve.org/CVERecord?id=CVE-2026-43009 Référence CVE CVE-2026-43013 https://www.cve.org/CVERecord?id=CVE-2026-43013 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31648 Référence CVE CVE-2026-31655 https://www.cve.org/CVERecord?id=CVE-2026-31655 Référence CVE CVE-2026-31664 https://www.cve.org/CVERecord?id=CVE-2026-31664 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31671 https://www.cve.org/CVERecord?id=CVE-2026-31671 Référence CVE CVE-2026-31673 https://www.cve.org/CVERecord?id=CVE-2026-31673 Référence CVE CVE-2026-31674 https://www.cve.org/CVERecord?id=CVE-2026-31674 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=CVE-2026-31678 Référence CVE CVE-2026-31683 https://www.cve.org/CVERecord?id=CVE-2026-31683 Référence CVE CVE-2026-31703 https://www.cve.org/CVERecord?id=CVE-2026-31703 Référence CVE CVE-2026-31729 https://www.cve.org/CVERecord?id=CVE-2026-31729 Référence CVE CVE-2026-31736 https://www.cve.org/CVERecord?id=CVE-2026-31736 Référence CVE CVE-2026-31758 https://www.cve.org/CVERecord?id=CVE-2026-31758 Référence CVE CVE-2026-31759 https://www.cve.org/CVERecord?id=CVE-2026-31759 Référence CVE CVE-2026-31767 https://www.cve.org/CVERecord?id=CVE-2026-31767 Référence CVE CVE-2026-31774 https://www.cve.org/CVERecord?id=CVE-2026-31774 Référence CVE CVE-2026-31778 https://www.cve.org/CVERecord?id=CVE-2026-31778 Référence CVE CVE-2026-34180 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014367LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、writebackサブシステムのinode_switch_wbs_work_fn()関数に存在したuse-after-freeの脆弱性が修正されました。この関数内部では、work構造体のリストをループ処理してアイテムを処理していましたが、workキューが保留中にもかかわらず、新しいアイテムがリストに追加されていない状態が発生し、解放されたwork構造体を参照し続ける問題がありました。このため、メモリ破壊の危険がありました。従来の参照カウントと作業キャンセルの仕組みだけでは問題の根本的な解決に不十分であったため、ループ構造を除去し、作業キューに登録される際に少なくとも最初のアイテムがリストに確実に存在することを保証する対策が取られました。これにより、不正なuse-after-freeを防止し、writebackの安全性が向上しました。

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: d072b38a64ddbc2d58c2e525a24af24ecbfebcb7 < 382cf81cae89e58d22b4bdc38891cd4d0b9ba921, ac7b2c21f2269d815ad0cdf0f8258d55185b805c < 19ec404b079be057b387643ba0c69bbcc5867c35, fabfc1fcddc5d8185722d4fde5f0968c4760b71e < 156cc63691c1f20905510b1007896e090355e6c2, e1b849cfa6b61f1c866a908c9e8dd9b5aaab820b < 028103656b84273c73e9e271cf95c9f3421f4b8a, e1b849cfa6b61f1c866a908c9e8dd9b5aaab820b < 9223e5f30403a9b506d6d0bff4f2e29a2d7d46af, e1b849cfa6b61f1c866a908c9e8dd9b5aaab820b < 6689f01d6740cf358932b3e97ee968c6099800d9, 6.18
Fixed
Linux: < 6.18, 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
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 1 May 2026 · Last source change 20 Aug 2026, 12:32 UTC · CWE-825 · Expired Pointer Dereference

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-26512
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
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 ↗

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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-26512↗Vendor CSAF · Red Hat Product Security↗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-31703 · cve.blacktree.nl