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

can: isotp: fix tx.buf use-after-free in isotp_sendmsg()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

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 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.6.19.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2026-31474 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-31474
172 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix tx.buf use-after-free in isotp_sendmsg() isotp_sendmsg() uses only cmpxchg() on so->tx.state to serialize access to so->tx.buf. isotp_release() waits for ISOTP_IDLE via wait_event_interruptible() and then calls kfree(so->tx.buf). If a signal interrupts the wait_event_interruptible() inside close() while tx.state is ISOTP_SENDING, the loop exits early and release proceeds to force ISOTP_SHUTDOWN and continues to kfree(so->tx.buf) while sendmsg may still be reading so->tx.buf for the final CAN frame in isotp_fill_dataframe(). The so->tx.buf can be allocated once when the standard tx.buf length needs to be extended. Move the kfree() of this potentially extended tx.buf to sk_destruct time when either isotp_sendmsg() and isotp_release() are done.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2026-24827

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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix tx.buf use-after-free in isotp_sendmsg() isotp_sendmsg() uses only cmpxchg() on so->tx.state to serialize access to so->tx.buf. isotp_release() waits for ISOTP_IDLE via wait_event_interruptible() and then calls kfree(so->tx.buf). If a signal interrupts the wait_event_interruptible() inside close() while tx.state is ISOTP_SENDING, the loop exits early and release proceeds to force ISOTP_SHUTDOWN and continues to kfree(so->tx.buf) while sendmsg may still be reading so->tx.buf for the final CAN frame in isotp_fill_dataframe(). The so->tx.buf can be allocated once when the standard tx.buf length needs to be extended. Move the kfree() of this potentially extended tx.buf to sk_destruct time when either isotp_sendmsg() and isotp_release() are done.

What

In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix tx.buf use-after-free in isotp_sendmsg() isotp_sendmsg() uses only cmpxchg() on so->tx.state to serialize access to so->tx.buf. isotp_release() waits for ISOTP_IDLE via wait_event_interruptible() and then calls kfree(so->tx.buf). If a signal interrupts the wait_event_interruptible() inside close() while tx.state is ISOTP_SENDING, the loop exits early and release proceeds to force ISOTP_SHUTDOWN and continues to kfree(so->tx.buf) while sendmsg may still be reading so->tx.buf for the final CAN frame in isotp_fill_dataframe(). The so->tx.buf can be allocated once when the standard tx.buf length needs to be extended. Move the kfree() of this potentially extended tx.buf to sk_destruct time when either isotp_sendmsg() and isotp_release() are done.

Why

The product uses a signal handler that introduces a race condition.

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: can: isotp: fix tx.buf use-after-free in isotp_sendmsg() isotp_sendmsg() uses only cmpxchg() on so->tx.state to serialize access to so->tx.buf. isotp_release() waits for ISOTP_IDLE via wait_event_interruptible() and then calls kfree(so->tx.buf). If a signal interrupts the wait_event_interruptible() inside close() while tx.state is ISOTP_SENDING, the loop exits early and release proceeds to force ISOTP_SHUTDOWN and continues to kfree(so->tx.buf) while sendmsg may still be reading so->tx.buf for the final CAN frame in isotp_fill_dataframe(). The so->tx.buf can be allocated once when the standard tx.buf length needs to be extended. Move the kfree() of this potentially extended tx.buf to sk_destruct time when either isotp_sendmsg() and isotp_release() are done.

Why

The product uses a signal handler that introduces a race condition.

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 → Signal Handler 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-364 ↗

CWE-364: Signal Handler Race Condition. The product uses a signal handler that introduces a race condition.

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-364
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-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31470 https://www.cve.org/CVERecord?id=CVE-2026-31470 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31476 https://www.cve.org/CVERecord?id=CVE-2026-31476 Référence CVE CVE-2026-31477 https://www.cve.org/CVERecord?id=CVE-2026-31477 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31482 https://www.cve.org/CVERecord?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31487 https://www.cve.org/CVERecord?id=CVE-2026-31487 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31442 https://www.cve.org/CVERecord?id=CVE-2026-31442 Référence CVE CVE-2026-31443 https://www.cve.org/CVERecord?id=CVE-2026-31443 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31462 https://www.cve.org/CVERecord?id=CVE-2026-31462 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31482 https://www.cve.org/CVERecord?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31489 https://www.cve.org/CVERecord?id=CVE-2026-31489 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31500 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-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31470 https://www.cve.org/CVERecord?id=CVE-2026-31470 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31476 https://www.cve.org/CVERecord?id=CVE-2026-31476 Référence CVE CVE-2026-31477 https://www.cve.org/CVERecord?id=CVE-2026-31477 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31482 https://www.cve.org/CVERecord?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31487 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31438 Référence CVE CVE-2026-31439 https://www.cve.org/CVERecord?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=CVE-2026-31497 Référence CVE CVE-2026-31498 https://www.cve.org/CVERecord?id=CVE-2026-31498 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-31502 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-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31470 https://www.cve.org/CVERecord?id=CVE-2026-31470 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31476 https://www.cve.org/CVERecord?id=CVE-2026-31476 Référence CVE CVE-2026-31477 https://www.cve.org/CVERecord?id=CVE-2026-31477 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31482 https://www.cve.org/CVERecord?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31487 https://www.cve.org/CVERecord?id=

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

26:28742 Bulletin de sécurité Red Hat RHSA-2026:28748 du 24 juin 2026 https://access.redhat.com/errata/RHSA-2026:28748 Bulletin de sécurité Red Hat RHSA-2026:28750 du 24 juin 2026 https://access.redhat.com/errata/RHSA-2026:28750 Bulletin de sécurité Red Hat RHSA-2026:26528 du 25 juin 2026 https://access.redhat.com/errata/RHSA-2026:26528 Bulletin de sécurité Red Hat RHSA-2026:26542 du 25 juin 2026 https://access.redhat.com/errata/RHSA-2026:26542 Bulletin de sécurité Red Hat RHSA-2026:30129 du 25 juin 2026 https://access.redhat.com/errata/RHSA-2026:30129 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31636 https://www.cve.org/CVERecord?id=CVE-2026-31636 Référence CVE CVE-2026-31641 https://www.cve.org/CVERecord?id=CVE-2026-31641 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31772 https://www.cve.org/CVERecord?id=CVE-2026-31772 Référence CVE CVE-2026-31786 https://www.cve.org/CVERecord?id=CVE-2026-31786 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-35385 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-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31462 https://www.cve.org/CVERecord?id=CVE-2026-31462 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31470 https://www.cve.org/CVERecord?id=CVE-2026-31470 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31476 https://www.cve.org/CVERecord?id=CVE-2026-31476 Référence CVE CVE-2026-31477 https://www.cve.org/CVERecord?id=CVE-2026-31477 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31482 https://www.cve.org/CVERecord?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0519Multiples vulnérabilités dans Microsoft Azure Linux

sécurité Microsoft CVE-2026-31450 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31451 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31452 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31453 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31454 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31455 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31458 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31467 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31469 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31473 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31474 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31476 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31483 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31485 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31494 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31495 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31496 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31497 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31500 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31503 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31504 du 23 avril 2026 Bu

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。can: isotp: isotp_sendmsg()内のtx.bufの使用後解放の修正です。isotp_sendmsg()は、so-tx.bufへのアクセスを直列化するために、so-tx.stateに対してcmpxchg()のみを使用しています。isotp_release()はwait_event_interruptible()でISOTP_IDLEを待機し、その後kfree(so-tx.buf)を呼び出します。もしclose()内のwait_event_interruptible()がシグナルによって中断され、tx.stateがISOTP_SENDINGである場合、ループが早期に終了し、releaseは強制的にISOTP_SHUTDOWNへ進みます。sendmsgがまだisotp_fill_dataframe()で最終的なCANフレームのためにso-tx.bufを読み込んでいる最中にkfree(so-tx.buf)を続行してしまいます。so-tx.bufは、標準のtx.buf長を拡張する必要がある場合に1度だけ割り当てられます。この潜在的に拡張されたtx.bufのkfree()の呼び出しは、isotp_sendmsg()とisotp_release()のいずれも終了した時点のsk_destructのタイミングに移動されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.4, 6.6.131 ≤ 6.6.*, 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:22 UTC · CWE-364 · Signal Handler 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-24827
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-24827↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-31474 · cve.blacktree.nl