BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-68302High confidence

net: sxgbe: fix potential NULL dereference in sxgbe_rx()

Linux · Linux

7.5HighCVSS 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:High, 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.46% 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 30 daysRemediation target: Within 180 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.63-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.159-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.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
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-2025-203778

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: net: sxgbe: fix potential NULL dereference in sxgbe_rx() Currently, when skb is null, the driver prints an error and then dereferences skb on the next line. To fix this, let's add a 'break' after the error message to switch to sxgbe_rx_refill(), which is similar to the approach taken by the other drivers in this particular case, e.g. calxeda with xgmac_rx(). Found during a code review.

What

In the Linux kernel, the following vulnerability has been resolved: net: sxgbe: fix potential NULL dereference in sxgbe_rx() Currently, when skb is null, the driver prints an error and then dereferences skb on the next line. To fix this, let's add a 'break' after the error message to switch to sxgbe_rx_refill(), which is similar to the approach taken by the other drivers in this particular case, e.g. calxeda with xgmac_rx(). Found during a code review.

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: net: sxgbe: fix potential NULL dereference in sxgbe_rx() Currently, when skb is null, the driver prints an error and then dereferences skb on the next line. To fix this, let's add a 'break' after the error message to switch to sxgbe_rx_refill(), which is similar to the approach taken by the other drivers in this particular case, e.g. calxeda with xgmac_rx(). Found during a code review.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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.

BSI · German · WID-SEC-2025-2868Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

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

d?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=CVE-2025-68288 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=CVE-2025-68288 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68321 https://www.cve.org/CVERecord?id=CVE-2025-68321 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68328 https://www.cve.org/CVERecord?id=CVE-2025-68328 Référence CVE CVE-2025-68330 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=CVE-2025-68288 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68321 https://www.cve.org/CVERecord?id=CVE-2025-68321 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68328 https://www.cve.org/CVERecord?id=CVE-2025-68328 Référence CVE CVE-2025-68330 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68293 Référence CVE CVE-2025-68294 https://www.cve.org/CVERecord?id=CVE-2025-68294 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68293 Référence CVE CVE-2025-68294 https://www.cve.org/CVERecord?id=CVE-2025-68294 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68293 Référence CVE CVE-2025-68294 https://www.cve.org/CVERecord?id=CVE-2025-68294 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68293 Référence CVE CVE-2025-68294 https://www.cve.org/CVERecord?id=CVE-2025-68294 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=CVE-2025-68288 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68309 https://www.cve.org/CVERecord?id=CVE-2025-68309 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=CVE-2025-68288 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68309 https://www.cve.org/CVERecord?id=CVE-2025-68309 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68293 https://www.cve.org/CVERecord?id=CVE-2025-68293 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68328 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=CVE-2025-68288 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68321 https://www.cve.org/CVERecord?id=CVE-2025-68321 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68328 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
Linux: 1edb9ca69e8a7988900fc0283e10550b5592164d < ac171c3c755499c9f87fe30b920602255f8b5648, 1edb9ca69e8a7988900fc0283e10550b5592164d < 18ef3ad1bb57dcf1a9ee61736039aedccf670b21, 1edb9ca69e8a7988900fc0283e10550b5592164d < 46e5332126596a2ca791140feab18ce1fc1a3c86, 1edb9ca69e8a7988900fc0283e10550b5592164d < 7fd789d6ea4915034eb6bcb72f6883c8151083e5, 1edb9ca69e8a7988900fc0283e10550b5592164d < 45b5b4ddb8d6bea5fc1625ff6f163bbb125d49cc, 1edb9ca69e8a7988900fc0283e10550b5592164d < 88f46c0be77bfe45830ac33102c75be7c34ac3f3, 1edb9ca69e8a7988900fc0283e10550b5592164d < f5bce28f6b9125502abec4a67d68eabcd24b3b17, 3.15
Fixed
Linux: < 3.15, 5.10.247 ≤ 5.10.*, 5.15.197 ≤ 5.15.*, 6.1.159 ≤ 6.1.*, 6.6.119 ≤ 6.6.*, 6.12.61 ≤ 6.12.*, 6.17.11 ≤ 6.17.*, 6.18 ≤ *
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 16 Dec 2025 · Last source change 5 Aug 2026, 12:10 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-2025-203778
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD not scheduled

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 ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-68302 · cve.blacktree.nl