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

rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present

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 1 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 2.26% 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.86-1Debian Security Tracker ↗Source updated 8 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-3Debian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.4-1Debian Security Tracker ↗Source updated 8 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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-43500 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: "Dirty Frag" RxRPC variant is a new universal Local Privilege Escalation (LPE) vulnerability in the Linux kernel
277 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's RxRPC networking subsystem. When a socket buffer carrying a page-cache reference reaches the RxRPC authentication verification path, the kernel performs an in-place decryption directly on the referenced page without first isolating the buffer. A low-privileged local attacker can exploit this behavior to corrupt the page-cache contents of readable files, including sensitive system files such as /etc/passwd, and obtain root privileges. Exploitation does not require unprivileged user or network namespaces, but depends on the RxRPC protocol stack being available on the target system.
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-29037

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE handler in rxrpc_verify_response() copy the skb to a linear one before calling into the security ops only when skb_cloned() is true. An skb that is not cloned but still carries externally-owned paged fragments (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via __ip_append_data, or a chained skb_has_frag_list()) falls through to the in-place decryption path, which binds the frag pages directly into the AEAD/skcipher SGL via skb_to_sgvec(). Extend the gate to also unshare when skb_has_frag_list() or skb_has_shared_frag() is true. This catches the splice-loopback vector and other externally-shared frag sources while preserving the zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC page_pool RX, GRO). The OOM/trace handling already in place is reused.

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE handler in rxrpc_verify_response() copy the skb to a linear one before calling into the security ops only when skb_cloned() is true. An skb that is not cloned but still carries externally-owned paged fragments (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via __ip_append_data, or a chained skb_has_frag_list()) falls through to the in-place decryption path, which binds the frag pages directly into the AEAD/skcipher SGL via skb_to_sgvec(). Extend the gate to also unshare when skb_has_frag_list() or skb_has_shared_frag() is true. This catches the splice-loopback vector and other externally-shared frag sources while preserving the zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC page_pool RX, GRO). The OOM/trace handling already in place is reused.

What

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE handler in rxrpc_verify_response() copy the skb to a linear one before calling into the security ops only when skb_cloned() is true. An skb that is not cloned but still carries externally-owned paged fragments (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via __ip_append_data, or a chained skb_has_frag_list()) falls through to the in-place decryption path, which binds the frag pages directly into the AEAD/skcipher SGL via skb_to_sgvec(). Extend the gate to also unshare when skb_has_frag_list() or skb_has_shared_frag() is true. This catches the splice-loopback vector and other externally-shared frag sources while preserving the zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC page_pool RX, GRO). The OOM/trace handling already in place is reused.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE handler in rxrpc_verify_response() copy the skb to a linear one before calling into the security ops only when skb_cloned() is true. An skb that is not cloned but still carries externally-owned paged fragments (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via __ip_append_data, or a chained skb_has_frag_list()) falls through to the in-place decryption path, which binds the frag pages directly into the AEAD/skcipher SGL via skb_to_sgvec(). Extend the gate to also unshare when skb_has_frag_list() or skb_has_shared_frag() is true. This catches the splice-loopback vector and other externally-shared frag sources while preserving the zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC page_pool RX, GRO). The OOM/trace handling already in place is reused.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 → Out-of-bounds Write → 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-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-29037Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE handler in rxrpc_verify_response() copy the skb to a linear one before calling into the security ops only when skb_cloned() is true. An skb that is not cloned but still carries externally-owned paged fragments (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via __ip_append_data, or a chained skb_has_frag_list()) falls through to the in-place decryption path, which binds the frag pages directly into the AEAD/skcipher SGL via skb_to_sgvec(). Extend the gate to also unshare when skb_has_frag_list() or skb_has_shared_frag() is true. This catches the splice-loopback vector and other externally-shared frag sources while preserving the zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC page_pool RX, GRO). The OOM/trace handling already in place is reused.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2437Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-1430Linux Kernel (Dirty Frag): Mehrere Schwachstellen ermöglichen Erlangen von Administratorrechten

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Administratorrechte zu erlangen.

Official advisory ↗
BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-524Mitel security advisory (AV26-524)

On May 28, 2026, Mitel published a security advisory to address vulnerabilities in the following products:

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-509[Control Systems] Moxa security advisory (AV26-509)

On May 26, 2026, Moxa published a security advisory to address vulnerabilities in the following products:

Official advisory ↗
Canadian Centre for Cyber Security · English · AL26-011AL26-011 - Vulnerabilities affecting Linux - CVE-2026-43284 and CVE-2026-43500

An Alert is used to raise awareness of a recently identified cyber threat that may impact cyber information assets, and to provide additional detection and mitigation advice to recipients. The Canadian Centre for Cyber Security (Cyber Centre) is also available to provide additional assistance regarding the content of this Alert upon request.

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

d?id=CVE-2025-68724 Référence CVE CVE-2026-12505 https://www.cve.org/CVERecord?id=CVE-2026-12505 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-46086 https://www.cve.org/CVERecord?id=CVE-2026-46086 Référence CVE CVE-2026-46116 https://www.cve.org/CVERecord?id=CVE-2026-46116 Référence CVE CVE-2026-46135 https://www.cve.org/CVERecord?id=CVE-2026-46135 Référence CVE CVE-2026-46189 https://www.cve.org/CVERecord?id=CVE-2026-46189 Référence CVE CVE-2026-46209 https://www.cve.org/CVERecord?id=CVE-2026-46209 Référence CVE CVE-2026-52923 https://www.cve.org/CVERecord?id=CVE-2026-52923 Référence CVE CVE-2026-52950 https://www.cve.org/CVERecord?id=CVE-2026-52950 Référence CVE CVE-2026-52976 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-43491 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 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-43491 Référence CVE CVE-2026-43492 https://www.cve.org/CVERecord?id=CVE-2026-43492 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43495 https://www.cve.org/CVERecord?id=CVE-2026-43495 Référence CVE CVE-2026-43496 https://www.cve.org/CVERecord?id=CVE-2026-43496 Référence CVE CVE-2026-43497 https://www.cve.org/CVERecord?id=CVE-2026-43497 Référence CVE CVE-2026-43498 https://www.cve.org/CVERecord?id=CVE-2026-43498 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43502 https://www.cve.org/CVERecord?id=CVE-2026-43502 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45834 https://www.cve.org/CVERecord?id=CVE-2026-45834 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45836 https://www.cve.org/CVERecord?id=CVE-2026-45836 Référence CVE CVE-2026-45837 https://www.cve.org/CVERecord?id=CVE-2026-45837 Référence CVE CVE-2026-45838 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-43384 Référence CVE CVE-2026-43402 https://www.cve.org/CVERecord?id=CVE-2026-43402 Référence CVE CVE-2026-43406 https://www.cve.org/CVERecord?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=CVE-2026-45847 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45849 https://www.cve.org/CVERecord?id=CVE-2026-45849 Référence CVE CVE-2026-45851 https://www.cve.org/CVERecord?id=CVE-2026-45851 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 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-43384 Référence CVE CVE-2026-43402 https://www.cve.org/CVERecord?id=CVE-2026-43402 Référence CVE CVE-2026-43406 https://www.cve.org/CVERecord?id=CVE-2026-43406 Référence CVE CVE-2026-43407 https://www.cve.org/CVERecord?id=CVE-2026-43407 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=CVE-2026-43414 Référence CVE CVE-2026-43491 https://www.cve.org/CVERecord?id=CVE-2026-43491 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45847 https://www.cve.org/CVERecord?id=CVE-2026-45847 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45849 https://www.cve.org/CVERecord?id=CVE-2026-45849 Référence CVE CVE-2026-45851 https://www.cve.org/CVERecord?id=CVE-2026-45851 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31419 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-47326 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43362 https://www.cve.org/CVERecord?id=CVE-2026-43362 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-47326 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-44917 https://www.cve.org/CVERecord?id=CVE-2026-44917 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-46447 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43329 Référence CVE CVE-2026-43330 https://www.cve.org/CVERecord?id=CVE-2026-43330 Référence CVE CVE-2026-43334 https://www.cve.org/CVERecord?id=CVE-2026-43334 Référence CVE CVE-2026-43365 https://www.cve.org/CVERecord?id=CVE-2026-43365 Référence CVE CVE-2026-43366 https://www.cve.org/CVERecord?id=CVE-2026-43366 Référence CVE CVE-2026-43419 https://www.cve.org/CVERecord?id=CVE-2026-43419 Référence CVE CVE-2026-43437 https://www.cve.org/CVERecord?id=CVE-2026-43437 Référence CVE CVE-2026-43441 https://www.cve.org/CVERecord?id=CVE-2026-43441 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Gestion détaillée du document le 05 juin 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

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

d?id=CVE-2026-31431 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=CVE-2026-31504 Référence CVE CVE-2026-31533 https://www.cve.org/CVERecord?id=CVE-2026-31533 Référence CVE CVE-2026-31676 https://www.cve.org/CVERecord?id=CVE-2026-31676 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43284 https://www.cve.org/CVERecord?id=CVE-2026-43284 Référence CVE CVE-2026-43494 https://www.cve.org/CVERecord?id=CVE-2026-43494 Référence CVE CVE-2026-43500 https://www.cve.org/CVERecord?id=CVE-2026-43500 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45966 https://www.cve.org/CVERecord?id=CVE-2026-45966 Référence CVE CVE-2026-45998 https://www.cve.org/CVERecord?id=CVE-2026-45998 Référence CVE CVE-2026-46000 https://www.cve.org/CVERecord?id=CVE-2026-46000 Référence CVE CVE-2026-46028 https://www.cve.org/CVERecord?id=CVE-2026-46028 Référence CVE CVE-2026-46300 https://www.cve.org/CVERecord?id=CVE-2026-46300 Référence CVE CVE-2026-46333 https://www.cve.org/CVERecord?id=CVE-2026-46333 Référence CVE CVE-2026-47326 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans les produits Mitel. Elles permettent à un attaquant de provoquer une élévation de privilèges.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoquer un contournement de la politique de sécurité et un problème de sécurité non spécifié par l'éditeur.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provoquer une élévation de privilèges, un déni de service à distance et une atteinte à la confidentialité des données.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Elles permettent à un attaquant de provoquer un déni de service et un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-015103LinuxのLinux Kernelにおける境界外書き込みに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。rxrpcでは、ページ化された断片が存在する場合にDATA/RESPONSEパケットも共有解除するように対応しました。rxrpc_input_call_event()内のDATAパケットハンドラおよびrxrpc_verify_response()内のRESPONSEハンドラは、skb_cloned()が真の場合にのみ、セキュリティ操作呼び出し前にskbをリニアにコピーします。クローンされていないが外部所有のページ断片（例：splice()によってUDPソケットに__ip_append_data経由で渡されるSKBFL_SHARED_FRAGが設定されたもの、またはチェインされたskb_has_frag_list()を持つskb）はインプレース復号化経路へ進み、fragページをskb_to_sgvec()を介して直接AEAD/skcipherのSGLに束縛します。skb_has_frag_list()またはskb_has_shared_frag()が真の場合にも共有解除を拡張し、splice-ループバックベクトルやその他の外部共有fragソースを検出します。一方で、fragsがカーネル専用（例：NICのpage_pool RX、GRO）のskbに対してはゼロコピー高速経路を維持します。既存のOOM/トレース処理も再利用されます。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-016978Linuxカーネルにおける複数の脆弱性

CERT/CCから本件に関するアドバイザリが公表されました。 VU#980487: Local privilege escalation in Linux Kernel (Dirty Frag) VU#260001: Linux kernel contains local privilege escalation vulnerability (Copy Fail)

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6787Linux Kernel 보안 업데이트 권고

Linux Kernel에서 발생하는 Out-of-bounds Write 취약점(CVE-2026-43500) [8]~[10][12]

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: patch: 7.1, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < aa54b1d27fe0c2b78e664a34fd0fdf7cd1960d71, 5.3, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < d45179f8795222ce858770dc619abe51f9d24411, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 3eae0f4f9f7206a4801efa5e0235c25bbd5a412c, patch: 6.6.140, patch: 6.12.88, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 7c504ffab3efce8f7e4f463b314ae31030bdf18b, patch: 6.18.29, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 3711382a77342a9a1c3d2e7330dcfc7ea927f568, patch: 7.0.6, patch: 0
Fixed
Linux: < 5.3, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.29 ≤ 6.18.*, 7.0.6 ≤ 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 11 May 2026 · Last source change 1 Sept 2026, 12:05 UTC · CWE-787 · Out-of-bounds Write

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-29037
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.
    Before
    no BlackTree article
    After
    1 BlackTree article
    BlackTree editorial ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 7c504ffab3efce8f7e4f463b314ae31030bdf18b; d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 3711382a77342a9a1c3d2e7330dcfc7ea927f568; d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 3eae0f4f9f7206a4801efa5e0235c25bbd5a412c; d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < d45179f8795222ce858770dc619abe51f9d24411; d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < aa54b1d27fe0c2b78e664a34fd0fdf7cd1960d71; 5.3 · Fixed: < 5.3; 6.6.140 ≤ 6.6.*; 6.12.88 ≤ 6.12.*; 6.18.29 ≤ 6.18.*; 7.0.6 ≤ 7.0.*; 7.1 ≤ *
    After
    Linux: d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 7c504ffab3efce8f7e4f463b314ae31030bdf18b, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 3711382a77342a9a1c3d2e7330dcfc7ea927f568, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < 3eae0f4f9f7206a4801efa5e0235c25bbd5a412c, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < d45179f8795222ce858770dc619abe51f9d24411, d0d5c0cd1e711c98703f3544c1e6fc1372898de5 < aa54b1d27fe0c2b78e664a34fd0fdf7cd1960d71, 5.3 · Fixed: Linux: < 5.3, 6.6.140 ≤ 6.6.*, 6.12.88 ≤ 6.12.*, 6.18.29 ≤ 6.18.*, 7.0.6 ≤ 7.0.*, 7.1 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-29037↗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-43500 · cve.blacktree.nl