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

phonet: pep: fix use-after-free in pep_get_sb()

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 35 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.54% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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: Within 3 daysRemediation target: Within 90 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 35 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.

25 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.101-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-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.

2 current
CVE-2026-68144 · CSAF 2.0 · revision 6 · interimSUSE Product Security TeamCVE-2026-68144
376 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68144 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: phonet: pep: fix use-after-free in pep_get_sb()
1 known affected

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

  • openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in the Linux kernel's Phonet subsystem. When processing Phonet packets, a use-after-free vulnerability exists in the `pep_get_sb()` function. This occurs because the function does not correctly handle situations where packet data might be relocated in memory, leading to the use of an outdated memory address. A local attacker could exploit this to cause a system crash (denial of service) or potentially execute arbitrary code, leading to a compromise of the system.
Remediation
Affected
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-55527

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.

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
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 35 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: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.

What

In the Linux kernel, the following vulnerability has been resolved: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. 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
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-55527Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: phonet: pep: fix use-after-free in pep_get_sb() pep_get_sb() doesn't consider that pskb_may_pull() might have relocated the skb data, and continue to access the older pointer, causing UAF. Reproduced under KASAN: BUG: KASAN: slab-use-after-free in pep_get_sb+0x234/0x3b0 Read of size 1 at addr ff11000105510f50 by task repro/157 pep_get_sb+0x234/0x3b0 pipe_handler_do_rcv+0x5f7/0xa10 pep_do_rcv+0x203/0x410 __sk_receive_skb+0x471/0x4a0 phonet_rcv+0x5b3/0x6c0 __netif_receive_skb+0xcc/0x1d0 Refetch the header with skb_header_pointer() after pskb_may_pull(), so the possibly stale pointer is no longer dereferenced. There are better ways to solve this, but, this is the less instrusive one.

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

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

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

d?id=CVE-2026-68133 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68139 https://www.cve.org/CVERecord?id=CVE-2026-68139 Référence CVE CVE-2026-68141 https://www.cve.org/CVERecord?id=CVE-2026-68141 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68145 https://www.cve.org/CVERecord?id=CVE-2026-68145 Référence CVE CVE-2026-68148 https://www.cve.org/CVERecord?id=CVE-2026-68148 Référence CVE CVE-2026-68149 https://www.cve.org/CVERecord?id=CVE-2026-68149 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=CVE-2026-68153 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68155 https://www.cve.org/CVERecord?id=CVE-2026-68155 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68091 Référence CVE CVE-2026-68092 https://www.cve.org/CVERecord?id=CVE-2026-68092 Référence CVE CVE-2026-68117 https://www.cve.org/CVERecord?id=CVE-2026-68117 Référence CVE CVE-2026-68123 https://www.cve.org/CVERecord?id=CVE-2026-68123 Référence CVE CVE-2026-68124 https://www.cve.org/CVERecord?id=CVE-2026-68124 Référence CVE CVE-2026-68127 https://www.cve.org/CVERecord?id=CVE-2026-68127 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68147 https://www.cve.org/CVERecord?id=CVE-2026-68147 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=CVE-2026-68159 Référence CVE CVE-2026-68160 https://www.cve.org/CVERecord?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68132 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68140 https://www.cve.org/CVERecord?id=CVE-2026-68140 Référence CVE CVE-2026-68141 https://www.cve.org/CVERecord?id=CVE-2026-68141 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68146 https://www.cve.org/CVERecord?id=CVE-2026-68146 Référence CVE CVE-2026-68147 https://www.cve.org/CVERecord?id=CVE-2026-68147 Référence CVE CVE-2026-68148 https://www.cve.org/CVERecord?id=CVE-2026-68148 Référence CVE CVE-2026-68151 https://www.cve.org/CVERecord?id=CVE-2026-68151 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=CVE-2026-68153 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68155 https://www.cve.org/CVERecord?id=CVE-2026-68155 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68133 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68139 https://www.cve.org/CVERecord?id=CVE-2026-68139 Référence CVE CVE-2026-68140 https://www.cve.org/CVERecord?id=CVE-2026-68140 Référence CVE CVE-2026-68141 https://www.cve.org/CVERecord?id=CVE-2026-68141 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68145 https://www.cve.org/CVERecord?id=CVE-2026-68145 Référence CVE CVE-2026-68146 https://www.cve.org/CVERecord?id=CVE-2026-68146 Référence CVE CVE-2026-68147 https://www.cve.org/CVERecord?id=CVE-2026-68147 Référence CVE CVE-2026-68148 https://www.cve.org/CVERecord?id=CVE-2026-68148 Référence CVE CVE-2026-68149 https://www.cve.org/CVERecord?id=CVE-2026-68149 Référence CVE CVE-2026-68151 https://www.cve.org/CVERecord?id=CVE-2026-68151 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=

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: < 2.6.28, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 6.18.*, 7.1.6 ≤ 7.1.*, 7.2 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 19 Aug 2026, 16:30 UTC · CWE not yet assigned

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-55527
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    bpftool as a component of Red Hat Enterprise Linux 7; kernel as a component of Red Hat Enterprise Linux 7; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7; kernel-bootwrapper as a component of Red Hat Enterprise Linux 7; kernel-debug as a component of Red Hat Enterprise Linux 7; kernel-debug-devel as a component of Red Hat Enterprise Linux 7; kernel-devel as a component of Red Hat Enterprise Linux 7; kernel-doc as a component of Red Hat Enterprise Linux 7; kernel-headers as a component of Red Hat Enterprise Linux 7; kernel-kdump as a component of Red Hat Enterprise Linux 7; kernel-kdump-devel as a component of Red Hat Enterprise Linux 7; kernel-tools as a component of Red Hat Enterprise Linux 7; kernel-tools-libs as a component of Red Hat Enterprise Linux 7; kernel-tools-libs-devel as a component of Red Hat Enterprise Linux 7; kernel.src as a component of Red Hat Enterprise Linux 7; perf as a component of Red Hat Enterprise Linux 7; python-perf as a component of Red Hat Enterprise Linux 7; bpftool as a component of Red Hat Enterprise Linux 8; kernel as a component of Red Hat Enterprise Linux 8; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 8; kernel-abi-whitelists as a component of Red Hat Enterprise Linux 8; kernel-core as a component of Red Hat Enterprise Linux 8; kernel-cross-headers as a component of Red Hat Enterprise Linux 8; kernel-debug as a component of Red Hat Enterprise Linux 8; kernel-debug-core as a component of Red Hat Enterprise Linux 8; kernel-debug-devel as a component of Red Hat Enterprise Linux 8; kernel-debug-modules as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 8; kernel-debug-modules-internal as a component of Red Hat Enterprise Linux 8; kernel-devel as a component of Red Hat Enterprise Linux 8; and 126 more
    After
    openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/c4a52cb4da8d57d060b1d52085d25147a238dac2; removed remediation: git.kernel.org/8d931a75a38b9bb584a4071f5ebbd52755fc35ee.
    Before
    remediation: git.kernel.org/8d931a75a38b9bb584a4071f5ebbd52755fc35ee
    After
    remediation: git.kernel.org/c4a52cb4da8d57d060b1d52085d25147a238dac2
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    9641458d3ec42def729fde64669abf07f3220cd5 < 8d931a75a38b9bb584a4071f5ebbd52755fc35ee; 9641458d3ec42def729fde64669abf07f3220cd5 < 17f78c0c0d41d738ee236eb6e841e39395188054; 9641458d3ec42def729fde64669abf07f3220cd5 < a48a889b60f73edb0399a8b08284a2ab0bd0295f; 9641458d3ec42def729fde64669abf07f3220cd5 < 25e3641beb51333bfbb155af2fd2573a61113af2; 9641458d3ec42def729fde64669abf07f3220cd5 < 0f71f852a96af9685858ce59fda34ecbf85c283d; 2.6.28 · Fixed: < 2.6.28; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    9641458d3ec42def729fde64669abf07f3220cd5 < c4a52cb4da8d57d060b1d52085d25147a238dac2; 9641458d3ec42def729fde64669abf07f3220cd5 < df198743859fefba2f824115f8151dd62d7ad6d8; 9641458d3ec42def729fde64669abf07f3220cd5 < 1d81e19fc57a5ee55b4497d01bc0510d76fb9578; 9641458d3ec42def729fde64669abf07f3220cd5 < 8d931a75a38b9bb584a4071f5ebbd52755fc35ee; 9641458d3ec42def729fde64669abf07f3220cd5 < 17f78c0c0d41d738ee236eb6e841e39395188054; 9641458d3ec42def729fde64669abf07f3220cd5 < a48a889b60f73edb0399a8b08284a2ab0bd0295f; 9641458d3ec42def729fde64669abf07f3220cd5 < 25e3641beb51333bfbb155af2fd2573a61113af2; 9641458d3ec42def729fde64669abf07f3220cd5 < 0f71f852a96af9685858ce59fda34ecbf85c283d · Fixed: < 2.6.28; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*
    CNA ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    9641458d3ec42def729fde64669abf07f3220cd5 < 8d931a75a38b9bb584a4071f5ebbd52755fc35ee; 9641458d3ec42def729fde64669abf07f3220cd5 < 17f78c0c0d41d738ee236eb6e841e39395188054; 9641458d3ec42def729fde64669abf07f3220cd5 < a48a889b60f73edb0399a8b08284a2ab0bd0295f; 9641458d3ec42def729fde64669abf07f3220cd5 < 25e3641beb51333bfbb155af2fd2573a61113af2; 9641458d3ec42def729fde64669abf07f3220cd5 < 0f71f852a96af9685858ce59fda34ecbf85c283d; 2.6.28 · Fixed: < 2.6.28; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc5 ≤ *
    After
    9641458d3ec42def729fde64669abf07f3220cd5 < 8d931a75a38b9bb584a4071f5ebbd52755fc35ee; 9641458d3ec42def729fde64669abf07f3220cd5 < 17f78c0c0d41d738ee236eb6e841e39395188054; 9641458d3ec42def729fde64669abf07f3220cd5 < a48a889b60f73edb0399a8b08284a2ab0bd0295f; 9641458d3ec42def729fde64669abf07f3220cd5 < 25e3641beb51333bfbb155af2fd2573a61113af2; 9641458d3ec42def729fde64669abf07f3220cd5 < 0f71f852a96af9685858ce59fda34ecbf85c283d; 2.6.28 · Fixed: < 2.6.28; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    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-55527↗Vendor CSAF · SUSE Product Security Team↗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-68144 · cve.blacktree.nl