FKIE_CVE-2026-90059

Vulnerability from fkie_nvd - Published: 2026-09-17 17:16 - Updated: 2026-09-18 18:17
Severity
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: net: stmmac: restore NET_IP_ALIGN in the RX DMA offset Since the RX path was converted to zero-copy, the page pool page is handed to the stack directly as the skb head, and the offset the DMA engine writes at is what determines the alignment of the packet headers. Before the conversion the payload was copied into an skb obtained from napi_alloc_skb(), which reserves NET_SKB_PAD + NET_IP_ALIGN. The conversion moved the headroom into stmmac_rx_offset() but did not carry over NET_IP_ALIGN, so on architectures where NET_IP_ALIGN is 2 the IP header now lands misaligned: 64 (NET_SKB_PAD) + 14 (ethernet) + 20 (IP) = 98 Same for the XDP branch: 256 (XDP_PACKET_HEADROOM) + 14 (ethernet) + 20 (IP) = 290 On ARM32 this is fatal, because ldm and ldrd trap on unaligned addresses even when CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS is set. Any received echo request panics the machine, e.g: Unhandled fault: alignment exception (0x001) at 0x81873062 Internal error: : 1 [#1] SMP ARM Hardware name: Altera SOCFPGA Arria10 PC is at icmp_echo+0x38/0xa8 LR is at icmp_rcv+0x22c/0x370 Call trace: icmp_echo from icmp_rcv+0x22c/0x370 icmp_rcv from ip_protocol_deliver_rcu+0x2c/0x224 ip_protocol_deliver_rcu from ip_local_deliver+0xc8/0x1a0 ip_local_deliver from ip_sublist_rcv_finish+0x3c/0x50 ip_sublist_rcv_finish from ip_list_rcv_finish+0x110/0x118 ip_list_rcv_finish from ip_list_rcv+0xc8/0xdc ip_list_rcv from __netif_receive_skb_list_core+0x170/0x1c0 ... napi_complete_done from stmmac_napi_poll_rx+0xcb0/0x1030 Code: e24dd068 e59020a0 e28dc010 e0822001 (e8920003) Kernel panic - not syncing: Fatal exception in interrupt The faulting instruction is the ldm of *icmp_hdr(skb) in icmp_echo(). Fix by adding NET_IP_ALIGN back to the RX offset, which restores the alignment the stack used to get. Note that commit a955318fe67e ("stmmac: align RX buffers") made a similar change in 2021 and was reverted by commit 12d125b4574b ("stmmac: Revert "stmmac: align RX buffers"") because it caused packet corruption. That patch raised the offset from 0 without adjusting the buffer size accounting, so the DMA engine could arguably write past the end of the RX buffers, though this was never root caused. Commit df542f669307 ("net: stmmac: Switch to zero-copy in non-XDP RX path") since derives the page pool allocation from stmmac_rx_offset(), so the extra bytes are accounted for.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/23680bf5f8c69c923546b84a8e6c401bef8b88fe
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2ea42936416b29cca42b2c7bc7d3d3768f77c199
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/c0d3f9560cc890bc2d96d9f487584688ae6e5185
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2ea42936416b29cca42b2c7bc7d3d3768f77c199",
              "status": "affected",
              "version": "df542f669307918f054a17878ff6dd1ddbb2fe18",
              "versionType": "git"
            },
            {
              "lessThan": "c0d3f9560cc890bc2d96d9f487584688ae6e5185",
              "status": "affected",
              "version": "df542f669307918f054a17878ff6dd1ddbb2fe18",
              "versionType": "git"
            },
            {
              "lessThan": "23680bf5f8c69c923546b84a8e6c401bef8b88fe",
              "status": "affected",
              "version": "df542f669307918f054a17878ff6dd1ddbb2fe18",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/stmicro/stmmac/stmmac_main.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.52",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: stmmac: restore NET_IP_ALIGN in the RX DMA offset\n\nSince the RX path was converted to zero-copy, the page pool page is handed\nto the stack directly as the skb head, and the offset the DMA engine writes\nat is what determines the alignment of the packet headers.\n\nBefore the conversion the payload was copied into an skb obtained from\nnapi_alloc_skb(), which reserves NET_SKB_PAD + NET_IP_ALIGN. The\nconversion moved the headroom into stmmac_rx_offset() but did not carry\nover NET_IP_ALIGN, so on architectures where NET_IP_ALIGN is 2 the IP\nheader now lands misaligned:\n\n  64 (NET_SKB_PAD) + 14 (ethernet) + 20 (IP) = 98\n\nSame for the XDP branch:\n\n  256 (XDP_PACKET_HEADROOM) + 14 (ethernet) + 20 (IP) = 290\n\nOn ARM32 this is fatal, because ldm and ldrd trap on unaligned addresses\neven when CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS is set.\n\nAny received echo request panics the machine, e.g:\n\n  Unhandled fault: alignment exception (0x001) at 0x81873062\n  Internal error: : 1 [#1] SMP ARM\n  Hardware name: Altera SOCFPGA Arria10\n  PC is at icmp_echo+0x38/0xa8\n  LR is at icmp_rcv+0x22c/0x370\n  Call trace:\n   icmp_echo from icmp_rcv+0x22c/0x370\n   icmp_rcv from ip_protocol_deliver_rcu+0x2c/0x224\n   ip_protocol_deliver_rcu from ip_local_deliver+0xc8/0x1a0\n   ip_local_deliver from ip_sublist_rcv_finish+0x3c/0x50\n   ip_sublist_rcv_finish from ip_list_rcv_finish+0x110/0x118\n   ip_list_rcv_finish from ip_list_rcv+0xc8/0xdc\n   ip_list_rcv from __netif_receive_skb_list_core+0x170/0x1c0\n   ...\n   napi_complete_done from stmmac_napi_poll_rx+0xcb0/0x1030\n  Code: e24dd068 e59020a0 e28dc010 e0822001 (e8920003)\n  Kernel panic - not syncing: Fatal exception in interrupt\n\nThe faulting instruction is the ldm of *icmp_hdr(skb) in icmp_echo().\n\nFix by adding NET_IP_ALIGN back to the RX offset, which restores the\nalignment the stack used to get.\n\nNote that commit a955318fe67e (\"stmmac: align RX buffers\") made a similar\nchange in 2021 and was reverted by commit 12d125b4574b (\"stmmac: Revert\n\"stmmac: align RX buffers\"\") because it caused packet corruption. That\npatch raised the offset from 0 without adjusting the buffer size\naccounting, so the DMA engine could arguably write past the end of the RX\nbuffers, though this was never root caused.\nCommit df542f669307 (\"net: stmmac: Switch to zero-copy in non-XDP RX\npath\") since derives the page pool allocation from stmmac_rx_offset(), so\nthe extra bytes are accounted for."
    }
  ],
  "id": "CVE-2026-90059",
  "lastModified": "2026-09-18T18:17:40.213",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 7.5,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "NONE",
          "integrityImpact": "NONE",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 3.6,
        "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "type": "Secondary"
      }
    ]
  },
  "published": "2026-09-17T17:16:54.590",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/23680bf5f8c69c923546b84a8e6c401bef8b88fe"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2ea42936416b29cca42b2c7bc7d3d3768f77c199"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/c0d3f9560cc890bc2d96d9f487584688ae6e5185"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.