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

bnxt: fix head underflow on XDP head-grow

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 206 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.65% 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 206 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 22 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 · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-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-74269 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-74269
157 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-extra 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
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is = 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-74269 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: bnxt: fix head underflow on XDP head-grow
184 known affected

The vendor explicitly identifies these products as 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 `bnxt` driver, a component of the Linux kernel responsible for network card operations. This vulnerability involves a memory corruption issue that occurs during specific network data processing (XDP head-grow operations). An underflow in the driver's code can lead to incorrect management of memory, potentially resulting in a 'double free' error. If exploited, this could allow an attacker to cause a denial of service, making the system unavailable, or lead to other unpredictable system behavior.
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-59416

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is < 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is >= 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.

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 206 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: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is < 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is >= 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.

What

In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is < 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is >= 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.

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 disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is < 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is >= 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.

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 disrupt the affected service.

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 → disrupt the affected service
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.
NetworkUnauthenticatedDenial of service
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-59416Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bnxt: fix head underflow on XDP head-grow The xdp.py test test_xdp_native_adjst_head_grow_data crashes when run on a bnxt machine (and also crashes in NIPA). It seems that the bug is an underflow in bnxt_rx_multi_page_skb, which builds the skb head: napi_build_skb(data_ptr - bp->rx_offset, rxr->rx_page_size); The problem with this expression is that in page mode, rx_offset is: bp->rx_offset = NET_IP_ALIGN + XDP_PACKET_HEADROOM; Which evaluates (at least on x86_64) to 258. The test test_xdp_native_adjst_head_grow_data tests a case where the head is adjusted by -256. When this test runs, data_ptr is shifted to frag_start + 2 (where frag_start = page_address(page) + offset). Then, bnxt_rx_multi_page_skb is invoked and the napi_build_skb expression subtracts 258, landing at an address before frag_start. This could be either the previous fragment or the previous physical page when the offset is < 256 (e.g. if the fragment started at offset 0). When the skb is freed, the page pool fragment reference is dropped on either the wrong page or the wrong frag of the right page. In either case, the corrupted reference count can lead to the page being prematurely recycled while still in use. Once (incorrectly) recycled, it can be handed out again and on driver teardown this would result in a double free. The commit under fixes updated this code to handle the case where the native page size is >= 64k, but it unintentionally broke the head grow case. To fix this, add an offset field to struct bnxt_sw_rx_bd, mirroring the existing offset field in struct bnxt_sw_rx_agg_bd. Populate it on allocation and preserve it on reuse. In bnxt_rx_multi_page_skb, use the newly added offset field to compute the fragment start and pass that to napi_build_skb. Adjust the layout with skb_reserve. There are two cases, the non-adjustment case and the adjustment case. In both cases, the skb is built at page_address(page) + offset to account for the case where the native page size >= 64K and skb_reserve is called with data_ptr - (page_address(page) + offset). That difference equals bp->rx_offset when data_ptr was not moved, or bp->rx_offset + xdp_adjust when XDP adjusted the head. Re-running the failing test with this commit applied causes the test to run successfully to completion. The other rx_skb_func implementations don't have this issue.

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 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-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-72491 Référence CVE CVE-2026-72493 https://www.cve.org/CVERecord?id=CVE-2026-72493 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-72501 https://www.cve.org/CVERecord?id=CVE-2026-72501 Référence CVE CVE-2026-74255 https://www.cve.org/CVERecord?id=CVE-2026-74255 Référence CVE CVE-2026-74267 https://www.cve.org/CVERecord?id=CVE-2026-74267 Référence CVE CVE-2026-74268 https://www.cve.org/CVERecord?id=CVE-2026-74268 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74287 https://www.cve.org/CVERecord?id=CVE-2026-74287 Référence CVE CVE-2026-74310 https://www.cve.org/CVERecord?id=CVE-2026-74310 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74350 https://www.cve.org/CVERecord?id=CVE-2026-74350 Référence CVE CVE-2026-74361 https://www.cve.org/CVERecord?id=CVE-2026-74361 Référence CVE CVE-2026-74376 https://www.cve.org/CVERecord?id=CVE-2026-74376 Référence CVE CVE-2026-74384 https://www.cve.org/CVERecord?id=CVE-2026-74384 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72497 https://www.cve.org/CVERecord?id=CVE-2026-72497 Référence CVE CVE-2026-72499 https://www.cve.org/CVERecord?id=CVE-2026-72499 Référence CVE CVE-2026-72500 https://www.cve.org/CVERecord?id=CVE-2026-72500 Référence CVE CVE-2026-72501 https://www.cve.org/CVERecord?id=CVE-2026-72501 Référence CVE CVE-2026-72502 https://www.cve.org/CVERecord?id=CVE-2026-72502 Référence CVE CVE-2026-74255 https://www.cve.org/CVERecord?id=CVE-2026-74255 Référence CVE CVE-2026-74261 https://www.cve.org/CVERecord?id=CVE-2026-74261 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74270 https://www.cve.org/CVERecord?id=CVE-2026-74270 Référence CVE CVE-2026-74282 https://www.cve.org/CVERecord?id=CVE-2026-74282 Référence CVE CVE-2026-74284 https://www.cve.org/CVERecord?id=CVE-2026-74284 Référence CVE CVE-2026-74286 https://www.cve.org/CVERecord?id=CVE-2026-74286 Référence CVE CVE-2026-74296 https://www.cve.org/CVERecord?id=CVE-2026-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74307 https://www.cve.org/CVERecord?id=CVE-2026-74307 Référence CVE CVE-2026-74308 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-72491 Référence CVE CVE-2026-72493 https://www.cve.org/CVERecord?id=CVE-2026-72493 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-72501 https://www.cve.org/CVERecord?id=CVE-2026-72501 Référence CVE CVE-2026-74255 https://www.cve.org/CVERecord?id=CVE-2026-74255 Référence CVE CVE-2026-74267 https://www.cve.org/CVERecord?id=CVE-2026-74267 Référence CVE CVE-2026-74268 https://www.cve.org/CVERecord?id=CVE-2026-74268 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74287 https://www.cve.org/CVERecord?id=CVE-2026-74287 Référence CVE CVE-2026-74310 https://www.cve.org/CVERecord?id=CVE-2026-74310 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74350 https://www.cve.org/CVERecord?id=CVE-2026-74350 Référence CVE CVE-2026-74361 https://www.cve.org/CVERecord?id=CVE-2026-74361 Référence CVE CVE-2026-74376 https://www.cve.org/CVERecord?id=CVE-2026-74376 Référence CVE CVE-2026-74384 https://www.cve.org/CVERecord?id=CVE-2026-74384 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-72497 https://www.cve.org/CVERecord?id=CVE-2026-72497 Référence CVE CVE-2026-72498 https://www.cve.org/CVERecord?id=CVE-2026-72498 Référence CVE CVE-2026-72499 https://www.cve.org/CVERecord?id=CVE-2026-72499 Référence CVE CVE-2026-72500 https://www.cve.org/CVERecord?id=CVE-2026-72500 Référence CVE CVE-2026-72501 https://www.cve.org/CVERecord?id=CVE-2026-72501 Référence CVE CVE-2026-72502 https://www.cve.org/CVERecord?id=CVE-2026-72502 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74296 https://www.cve.org/CVERecord?id=CVE-2026-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74318 https://www.cve.org/CVERecord?id=CVE-2026-74318 Référence CVE CVE-2026-74321 https://www.cve.org/CVERecord?id=CVE-2026-74321 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=CVE-2026-74394 Référence CVE CVE-2026-74395 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-72491 Référence CVE CVE-2026-72494 https://www.cve.org/CVERecord?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-72499 https://www.cve.org/CVERecord?id=CVE-2026-72499 Référence CVE CVE-2026-74255 https://www.cve.org/CVERecord?id=CVE-2026-74255 Référence CVE CVE-2026-74264 https://www.cve.org/CVERecord?id=CVE-2026-74264 Référence CVE CVE-2026-74267 https://www.cve.org/CVERecord?id=CVE-2026-74267 Référence CVE CVE-2026-74268 https://www.cve.org/CVERecord?id=CVE-2026-74268 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74279 https://www.cve.org/CVERecord?id=CVE-2026-74279 Référence CVE CVE-2026-74280 https://www.cve.org/CVERecord?id=CVE-2026-74280 Référence CVE CVE-2026-74287 https://www.cve.org/CVERecord?id=CVE-2026-74287 Référence CVE CVE-2026-74302 https://www.cve.org/CVERecord?id=CVE-2026-74302 Référence CVE CVE-2026-74305 https://www.cve.org/CVERecord?id=CVE-2026-74305 Référence CVE CVE-2026-74310 https://www.cve.org/CVERecord?id=CVE-2026-74310 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74350 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-72494 Référence CVE CVE-2026-72495 https://www.cve.org/CVERecord?id=CVE-2026-72495 Référence CVE CVE-2026-72496 https://www.cve.org/CVERecord?id=CVE-2026-72496 Référence CVE CVE-2026-72497 https://www.cve.org/CVERecord?id=CVE-2026-72497 Référence CVE CVE-2026-72498 https://www.cve.org/CVERecord?id=CVE-2026-72498 Référence CVE CVE-2026-72499 https://www.cve.org/CVERecord?id=CVE-2026-72499 Référence CVE CVE-2026-72500 https://www.cve.org/CVERecord?id=CVE-2026-72500 Référence CVE CVE-2026-72501 https://www.cve.org/CVERecord?id=CVE-2026-72501 Référence CVE CVE-2026-72502 https://www.cve.org/CVERecord?id=CVE-2026-72502 Référence CVE CVE-2026-74269 https://www.cve.org/CVERecord?id=CVE-2026-74269 Référence CVE CVE-2026-74296 https://www.cve.org/CVERecord?id=CVE-2026-74296 Référence CVE CVE-2026-74297 https://www.cve.org/CVERecord?id=CVE-2026-74297 Référence CVE CVE-2026-74318 https://www.cve.org/CVERecord?id=CVE-2026-74318 Référence CVE CVE-2026-74321 https://www.cve.org/CVERecord?id=CVE-2026-74321 Référence CVE CVE-2026-74334 https://www.cve.org/CVERecord?id=CVE-2026-74334 Référence CVE CVE-2026-74345 https://www.cve.org/CVERecord?id=CVE-2026-74345 Référence CVE CVE-2026-74394 https://www.cve.org/CVERecord?id=CVE-2026-74394 Référence CVE CVE-2026-74395 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: < 6.5, 6.18.53 ≤ 6.18.*, 7.1.5 ≤ 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 15 Aug 2026 · Last source change 21 Sept 2026, 13:13 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-23
European sourceENISA EUVD · EUVD-2026-59416
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. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/4c03275bc4435cc8e25f7f3f08aff58c0e783d8d; removed remediation: git.kernel.org/bb72b1c6755631c74b7e0878ee55bb81c06776c0.
    Before
    remediation: git.kernel.org/bb72b1c6755631c74b7e0878ee55bb81c06776c0
    After
    remediation: git.kernel.org/4c03275bc4435cc8e25f7f3f08aff58c0e783d8d
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < bb72b1c6755631c74b7e0878ee55bb81c06776c0; f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < e26657fe3b85c068b01f42bb0c602f242d643ba9; e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16; ae0e135dc900827687ecc684c2bbb57aae48d318; 6.1.45 < 6.2; 6.4.10 < 6.5; 6.5 · Fixed: < 6.5; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    After
    Linux: f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < 4c03275bc4435cc8e25f7f3f08aff58c0e783d8d, f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < bb72b1c6755631c74b7e0878ee55bb81c06776c0, f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < e26657fe3b85c068b01f42bb0c602f242d643ba9, e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16, ae0e135dc900827687ecc684c2bbb57aae48d318, 6.1.45 < 6.2, 6.4.10 < 6.5, 6.5 · Fixed: Linux: < 6.5, 6.18.53 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < bb72b1c6755631c74b7e0878ee55bb81c06776c0; f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < e26657fe3b85c068b01f42bb0c602f242d643ba9; e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16; ae0e135dc900827687ecc684c2bbb57aae48d318; 6.1.45 < 6.2; 6.4.10 < 6.5; 6.5 · Fixed: < 6.5; 7.1.5 ≤ 7.1.*; 7.2-rc1 ≤ *
    After
    f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < bb72b1c6755631c74b7e0878ee55bb81c06776c0; f6974b4c2d8e1062b5a52228ee47293c15b4ee1e < e26657fe3b85c068b01f42bb0c602f242d643ba9; e9f11bfc03fb0d3c86f91b8ae945bb10f7e19c16; ae0e135dc900827687ecc684c2bbb57aae48d318; 6.1.45 < 6.2; 6.4.10 < 6.5; 6.5 · Fixed: < 6.5; 7.1.5 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  4. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    CNA ↗
  5. CVSS scoreCVSS score changed from not recorded to 9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    9.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    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-59416↗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-74269 · cve.blacktree.nl