{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-40999",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-40999"
  ],
  "published": "2024-07-12T12:38:02Z",
  "summary": "net: ena: Add validation for completion descriptors consistency",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ena: Add validation for completion descriptors consistency\n\nValidate that `first` flag is set only for the first\ndescriptor in multi-buffer packets.\nIn case of an invalid descriptor, a reset will occur.\nA new reset reason for RX data corruption has been added.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-40999"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/42146ee5286f16f1674a84f7c274dcca65c6ff2e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b37b98a3a0c1198bafe8c2d9ce0bc845b4e7a9a7"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:52:36Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 9.8,
      "cvss_v3_severity": "Critical",
      "scenario": "AV:N - The vulnerable code is the NIC receive completion path (`ena_clean_rx_irq`/`ena_com_rx_pkt`), entered solely as a result of frames arriving from the network, and the multi-descriptor framing logic at fault is only exercised by large/scattered packets a remote peer generates at will. ENA is the standard NIC on internet-facing AWS EC2 instances, so the path is driven by remote, unauthenticated traffic.\nAC:L - No specific memory layout, victim state, or non-default configuration is required; the descriptor-framing path is exercised by ordinary multi-buffer RX traffic and the driver's cross-poll partial-packet state can be driven by sustained large-packet load. Per the rule to choose the higher severity when uncertain, the influenceable device-side framing condition is scored as Low rather than High.\nPR:N - Processing happens in NAPI/softirq context before any socket, filesystem, or authentication layer is reached, so no account or capability on the target is needed. A remote peer simply sends packets to the interface.\nUI:N - The RX completion path runs automatically whenever the interface is up and receiving traffic. No victim action of any kind is required.\nS:U - The mis-framed descriptors corrupt driver state and skb contents within the same kernel/host security authority. No VM, IOMMU, or sandbox boundary is crossed.\nC:H - Merged descriptor chains splice RX buffers belonging to unrelated packets into a single skb delivered to the network stack, and the accumulated `buf_offset`/`buf_len` can describe fragments extending past the real allocation, giving out-of-bounds reads. Stale page pointers reaching `skb_add_rx_frag()` constitute a use-after-free, which is scored High for confidentiality.\nI:H - The unguarded fragment loop can `page_ref_inc()` and `skb_add_rx_frag()` a stale or already-released page and DMA-unmap an already-unmapped buffer, producing double-free/UAF heap-corruption primitives; corrupted packet data is also injected into the stack. Memory corruption of this kind is exploitable for control-flow hijack and is scored High.\nA:H - A NULL `rx_info->page` reaching `page_ref_inc()`/`skb_add_rx_frag()` is an immediate kernel oops, and even the benign outcome is RX ring desync that stalls buffer replenishment and forces a full device reset, dropping network connectivity. Any kernel crash or hang is scored High."
    }
  }
}