CVE-2025-40290 (GCVE-0-2025-40290)

Vulnerability from cvelistv5 – Published: 2025-12-08 00:09 – Updated: 2026-08-05 12:09
VLAI
Title
xsk: avoid data corruption on cq descriptor number
Summary
In the Linux kernel, the following vulnerability has been resolved: xsk: avoid data corruption on cq descriptor number Since commit 30f241fcf52a ("xsk: Fix immature cq descriptor production"), the descriptor number is stored in skb control block and xsk_cq_submit_addr_locked() relies on it to put the umem addrs onto pool's completion queue. skb control block shouldn't be used for this purpose as after transmit xsk doesn't have control over it and other subsystems could use it. This leads to the following kernel panic due to a NULL pointer dereference. BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 2 UID: 1 PID: 927 Comm: p4xsk.bin Not tainted 6.16.12+deb14-cloud-amd64 #1 PREEMPT(lazy) Debian 6.16.12-1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 RIP: 0010:xsk_destruct_skb+0xd0/0x180 [...] Call Trace: <IRQ> ? napi_complete_done+0x7a/0x1a0 ip_rcv_core+0x1bb/0x340 ip_rcv+0x30/0x1f0 __netif_receive_skb_one_core+0x85/0xa0 process_backlog+0x87/0x130 __napi_poll+0x28/0x180 net_rx_action+0x339/0x420 handle_softirqs+0xdc/0x320 ? handle_edge_irq+0x90/0x1e0 do_softirq.part.0+0x3b/0x60 </IRQ> <TASK> __local_bh_enable_ip+0x60/0x70 __dev_direct_xmit+0x14e/0x1f0 __xsk_generic_xmit+0x482/0xb70 ? __remove_hrtimer+0x41/0xa0 ? __xsk_generic_xmit+0x51/0xb70 ? _raw_spin_unlock_irqrestore+0xe/0x40 xsk_sendmsg+0xda/0x1c0 __sys_sendto+0x1ee/0x200 __x64_sys_sendto+0x24/0x30 do_syscall_64+0x84/0x2f0 ? __pfx_pollwake+0x10/0x10 ? __rseq_handle_notify_resume+0xad/0x4c0 ? restore_fpregs_from_fpstate+0x3c/0x90 ? switch_fpu_return+0x5b/0xe0 ? do_syscall_64+0x204/0x2f0 ? do_syscall_64+0x204/0x2f0 ? do_syscall_64+0x204/0x2f0 entry_SYSCALL_64_after_hwframe+0x76/0x7e </TASK> [...] Kernel panic - not syncing: Fatal exception in interrupt Kernel Offset: 0x1c000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) Instead use the skb destructor_arg pointer along with pointer tagging. As pointers are always aligned to 8B, use the bottom bit to indicate whether this a single address or an allocated struct containing several addresses.
Assigner
Impacted products
Vendor Product Version
Linux Linux Affected: 30f241fcf52aaaef7ac16e66530faa11be78a865 , < c5ea2e50b5c9aa80c5b53526257540f0c26cd66d (git)
Affected: 30f241fcf52aaaef7ac16e66530faa11be78a865 , < 0ebc27a4c67d44e5ce88d21cdad8201862b78837 (git)
Affected: 932cb57e675a62982d4719e4b04e9f09a15a5baf (git)
Affected: 6.16.8 , < 6.17 (semver)
Create a notification for this product.
Linux Linux Affected: 6.17
Unaffected: 0 , < 6.17 (semver)
Unaffected: 6.17.11 , ≤ 6.17.* (semver)
Unaffected: 6.18 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/xdp/xsk.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c5ea2e50b5c9aa80c5b53526257540f0c26cd66d",
              "status": "affected",
              "version": "30f241fcf52aaaef7ac16e66530faa11be78a865",
              "versionType": "git"
            },
            {
              "lessThan": "0ebc27a4c67d44e5ce88d21cdad8201862b78837",
              "status": "affected",
              "version": "30f241fcf52aaaef7ac16e66530faa11be78a865",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "932cb57e675a62982d4719e4b04e9f09a15a5baf",
              "versionType": "git"
            },
            {
              "lessThan": "6.17",
              "status": "affected",
              "version": "6.16.8",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/xdp/xsk.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.17"
            },
            {
              "lessThan": "6.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.17.*",
              "status": "unaffected",
              "version": "6.17.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.18",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.17.11",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18",
                  "versionStartIncluding": "6.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.16.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxsk: avoid data corruption on cq descriptor number\n\nSince commit 30f241fcf52a (\"xsk: Fix immature cq descriptor\nproduction\"), the descriptor number is stored in skb control block and\nxsk_cq_submit_addr_locked() relies on it to put the umem addrs onto\npool\u0027s completion queue.\n\nskb control block shouldn\u0027t be used for this purpose as after transmit\nxsk doesn\u0027t have control over it and other subsystems could use it. This\nleads to the following kernel panic due to a NULL pointer dereference.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000000\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n PGD 0 P4D 0\n Oops: Oops: 0000 [#1] SMP NOPTI\n CPU: 2 UID: 1 PID: 927 Comm: p4xsk.bin Not tainted 6.16.12+deb14-cloud-amd64 #1 PREEMPT(lazy)  Debian 6.16.12-1\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\n RIP: 0010:xsk_destruct_skb+0xd0/0x180\n [...]\n Call Trace:\n  \u003cIRQ\u003e\n  ? napi_complete_done+0x7a/0x1a0\n  ip_rcv_core+0x1bb/0x340\n  ip_rcv+0x30/0x1f0\n  __netif_receive_skb_one_core+0x85/0xa0\n  process_backlog+0x87/0x130\n  __napi_poll+0x28/0x180\n  net_rx_action+0x339/0x420\n  handle_softirqs+0xdc/0x320\n  ? handle_edge_irq+0x90/0x1e0\n  do_softirq.part.0+0x3b/0x60\n  \u003c/IRQ\u003e\n  \u003cTASK\u003e\n  __local_bh_enable_ip+0x60/0x70\n  __dev_direct_xmit+0x14e/0x1f0\n  __xsk_generic_xmit+0x482/0xb70\n  ? __remove_hrtimer+0x41/0xa0\n  ? __xsk_generic_xmit+0x51/0xb70\n  ? _raw_spin_unlock_irqrestore+0xe/0x40\n  xsk_sendmsg+0xda/0x1c0\n  __sys_sendto+0x1ee/0x200\n  __x64_sys_sendto+0x24/0x30\n  do_syscall_64+0x84/0x2f0\n  ? __pfx_pollwake+0x10/0x10\n  ? __rseq_handle_notify_resume+0xad/0x4c0\n  ? restore_fpregs_from_fpstate+0x3c/0x90\n  ? switch_fpu_return+0x5b/0xe0\n  ? do_syscall_64+0x204/0x2f0\n  ? do_syscall_64+0x204/0x2f0\n  ? do_syscall_64+0x204/0x2f0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  \u003c/TASK\u003e\n [...]\n Kernel panic - not syncing: Fatal exception in interrupt\n Kernel Offset: 0x1c000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\n\nInstead use the skb destructor_arg pointer along with pointer tagging.\nAs pointers are always aligned to 8B, use the bottom bit to indicate\nwhether this a single address or an allocated struct containing several\naddresses."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerability is triggered by a local `sendto()`/`sendmsg()` syscall on an AF_XDP socket the attacker created and bound in generic (XDP_COPY) mode; no remote packet reception is involved in reaching the vulnerable destructor.\nAC:L - The attacker fully controls every precondition \u2014 creating the netns/veth pair, binding XDP_COPY to an interface with ifindex \u2265 2, and sending an IPv4/IPv6 frame \u2014 and the resulting `num_descs = ifindex \u003e 1` plus zeroed list head is deterministic, not a race or a memory-layout gamble.\nPR:L - `xsk_create()` requires only `ns_capable(net-\u003euser_ns, CAP_NET_RAW)`, which any unprivileged user obtains via `unshare -Urn`, and the veth setup needs only CAP_NET_ADMIN in that same user namespace; the reported oops was hit by a non-root UID 1 process.\nUI:N - The attacking process performs the entire sequence itself \u2014 socket, umem, bind, sendmsg \u2014 with no action required from any other user or victim.\nS:U - The corruption and its impact are confined to the kernel\u0027s own security authority; no hypervisor, IOMMU, or other trust boundary is crossed.\nC:H - The wild list walk executes `xskq_prod_write_addr(pool-\u003ecq, ..., pos-\u003eaddr)`, copying 8 bytes read from an uncontrolled kernel pointer into the completion ring that is mmap\u0027d directly into the attacker\u0027s address space, giving a kernel-memory disclosure channel; the accompanying slab corruption further enables info-leak primitives.\nI:H - `list_del()` on the clobbered head performs two kernel writes through foreign pointers, and `kmem_cache_free(xsk_tx_generic_cache, pos)` frees a non-cache pointer into the wrong slab \u2014 an arbitrary-free/UAF primitive \u2014 plus the bogus count desyncs the shared completion queue via the unchecked `q-\u003ecached_prod -= cnt`.\nA:H - The reported and reproducible outcome is a NULL pointer dereference inside a softirq, producing `Kernel panic - not syncing: Fatal exception in interrupt` \u2014 a full system crash, repeatable at will by an unprivileged local user."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:09:16.273Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c5ea2e50b5c9aa80c5b53526257540f0c26cd66d"
        },
        {
          "url": "https://git.kernel.org/stable/c/0ebc27a4c67d44e5ce88d21cdad8201862b78837"
        },
        {
          "url": "https://bugs.debian.org/1118437"
        }
      ],
      "title": "xsk: avoid data corruption on cq descriptor number",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-40290",
    "datePublished": "2025-12-08T00:09:08.370Z",
    "dateReserved": "2025-04-16T07:20:57.185Z",
    "dateUpdated": "2026-08-05T12:09:16.273Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-40290",
      "date": "2026-08-05",
      "epss": "0.00139",
      "percentile": "0.03698"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-40290\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-08T01:16:00.890\",\"lastModified\":\"2026-07-30T06:24:26.840\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nxsk: avoid data corruption on cq descriptor number\\n\\nSince commit 30f241fcf52a (\\\"xsk: Fix immature cq descriptor\\nproduction\\\"), the descriptor number is stored in skb control block and\\nxsk_cq_submit_addr_locked() relies on it to put the umem addrs onto\\npool\u0027s completion queue.\\n\\nskb control block shouldn\u0027t be used for this purpose as after transmit\\nxsk doesn\u0027t have control over it and other subsystems could use it. This\\nleads to the following kernel panic due to a NULL pointer dereference.\\n\\n BUG: kernel NULL pointer dereference, address: 0000000000000000\\n #PF: supervisor read access in kernel mode\\n #PF: error_code(0x0000) - not-present page\\n PGD 0 P4D 0\\n Oops: Oops: 0000 [#1] SMP NOPTI\\n CPU: 2 UID: 1 PID: 927 Comm: p4xsk.bin Not tainted 6.16.12+deb14-cloud-amd64 #1 PREEMPT(lazy)  Debian 6.16.12-1\\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014\\n RIP: 0010:xsk_destruct_skb+0xd0/0x180\\n [...]\\n Call Trace:\\n  \u003cIRQ\u003e\\n  ? napi_complete_done+0x7a/0x1a0\\n  ip_rcv_core+0x1bb/0x340\\n  ip_rcv+0x30/0x1f0\\n  __netif_receive_skb_one_core+0x85/0xa0\\n  process_backlog+0x87/0x130\\n  __napi_poll+0x28/0x180\\n  net_rx_action+0x339/0x420\\n  handle_softirqs+0xdc/0x320\\n  ? handle_edge_irq+0x90/0x1e0\\n  do_softirq.part.0+0x3b/0x60\\n  \u003c/IRQ\u003e\\n  \u003cTASK\u003e\\n  __local_bh_enable_ip+0x60/0x70\\n  __dev_direct_xmit+0x14e/0x1f0\\n  __xsk_generic_xmit+0x482/0xb70\\n  ? __remove_hrtimer+0x41/0xa0\\n  ? __xsk_generic_xmit+0x51/0xb70\\n  ? _raw_spin_unlock_irqrestore+0xe/0x40\\n  xsk_sendmsg+0xda/0x1c0\\n  __sys_sendto+0x1ee/0x200\\n  __x64_sys_sendto+0x24/0x30\\n  do_syscall_64+0x84/0x2f0\\n  ? __pfx_pollwake+0x10/0x10\\n  ? __rseq_handle_notify_resume+0xad/0x4c0\\n  ? restore_fpregs_from_fpstate+0x3c/0x90\\n  ? switch_fpu_return+0x5b/0xe0\\n  ? do_syscall_64+0x204/0x2f0\\n  ? do_syscall_64+0x204/0x2f0\\n  ? do_syscall_64+0x204/0x2f0\\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\\n  \u003c/TASK\u003e\\n [...]\\n Kernel panic - not syncing: Fatal exception in interrupt\\n Kernel Offset: 0x1c000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)\\n\\nInstead use the skb destructor_arg pointer along with pointer tagging.\\nAs pointers are always aligned to 8B, use the bottom bit to indicate\\nwhether this a single address or an allocated struct containing several\\naddresses.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"net/xdp/xsk.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"30f241fcf52aaaef7ac16e66530faa11be78a865\",\"lessThan\":\"c5ea2e50b5c9aa80c5b53526257540f0c26cd66d\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"30f241fcf52aaaef7ac16e66530faa11be78a865\",\"lessThan\":\"0ebc27a4c67d44e5ce88d21cdad8201862b78837\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"932cb57e675a62982d4719e4b04e9f09a15a5baf\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"6.16.8\",\"lessThan\":\"6.17\",\"versionType\":\"semver\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"net/xdp/xsk.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.17\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.17\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.17.11\",\"lessThanOrEqual\":\"6.17.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"references\":[{\"url\":\"https://bugs.debian.org/1118437\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/0ebc27a4c67d44e5ce88d21cdad8201862b78837\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/c5ea2e50b5c9aa80c5b53526257540f0c26cd66d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
    "redhat_vex": {
      "aggregate_severity": "None",
      "current_release_date": "2026-06-30T10:34:35+00:00",
      "cve": "CVE-2025-40290",
      "id": "CVE-2025-40290",
      "initial_release_date": "2025-12-08T00:00:00+00:00",
      "product_status:known_not_affected": "274",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: xsk: avoid data corruption on cq descriptor number",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-40290.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…