GHSA-RJ48-HQ74-H6FV

Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

fou: reject omitted FOU_ATTR_IPPROTO on FOU_ENCAP_DIRECT

Commit 7a9bc9e3f423 ("fou: Don't allow 0 for FOU_ATTR_IPPROTO.") added NLA_POLICY_MIN(NLA_U8, 1) to fou_nl_policy[FOU_ATTR_IPPROTO], which rejects an explicitly supplied FOU_ATTR_IPPROTO == 0 attribute with -ERANGE.

However, FOU_ATTR_IPPROTO is an optional netlink attribute. When a user sends FOU_CMD_ADD with FOU_ATTR_TYPE set to FOU_ENCAP_DIRECT and omits FOU_ATTR_IPPROTO entirely, nla_policy validation succeeds and parse_nl_config() leaves cfg->protocol as 0 (from memset(cfg, 0, sizeof(*cfg))). fou_create() then creates a FOU_ENCAP_DIRECT socket with fou->protocol == 0.

In fou_udp_recv(), returning -fou->protocol to udp_queue_rcv_one_skb() triggers IP protocol resubmission when fou->protocol > 0, whereas returning 0 tells the UDP tunnel layer that the skb was consumed without freeing it. When fou->protocol == 0, every packet received on the socket returns 0 from fou_udp_recv() and leaks the sk_buff.

Reject FOU_ENCAP_DIRECT when !cfg->protocol in fou_create() so that creating a direct encapsulation port without FOU_ATTR_IPPROTO fails with -EINVAL while leaving FOU_CMD_DEL and FOU_CMD_GET (which share parse_nl_config()) unaffected.

Tested in QEMU against Linux 7.3.0-rc3 by sending a FOU_CMD_ADD Generic Netlink request with FOU_ATTR_PORT = 5555 and FOU_ATTR_TYPE = FOU_ENCAP_DIRECT while omitting FOU_ATTR_IPPROTO. On the unfixed kernel, FOU_CMD_ADD succeeds (err = 0), FOU_CMD_GET reports fou->type = 1 and fou->protocol = 0, and sending 4000 UDP packets to 127.0.0.1:5555 leaks all 4000 sk_buffs (SUnreclaim in /proc/meminfo grows from 41456 kB to 59008 kB, +17552 kB); with this patch applied, FOU_CMD_ADD is rejected with -EINVAL (-22).

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-98541"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-10-18T16:17:05Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfou: reject omitted FOU_ATTR_IPPROTO on FOU_ENCAP_DIRECT\n\nCommit 7a9bc9e3f423 (\"fou: Don\u0027t allow 0 for FOU_ATTR_IPPROTO.\") added\nNLA_POLICY_MIN(NLA_U8, 1) to fou_nl_policy[FOU_ATTR_IPPROTO], which\nrejects an explicitly supplied FOU_ATTR_IPPROTO == 0 attribute with\n-ERANGE.\n\nHowever, FOU_ATTR_IPPROTO is an optional netlink attribute. When a user\nsends FOU_CMD_ADD with FOU_ATTR_TYPE set to FOU_ENCAP_DIRECT and omits\nFOU_ATTR_IPPROTO entirely, nla_policy validation succeeds and\nparse_nl_config() leaves cfg-\u003eprotocol as 0 (from memset(cfg, 0,\nsizeof(*cfg))). fou_create() then creates a FOU_ENCAP_DIRECT socket with\nfou-\u003eprotocol == 0.\n\nIn fou_udp_recv(), returning -fou-\u003eprotocol to udp_queue_rcv_one_skb()\ntriggers IP protocol resubmission when fou-\u003eprotocol \u003e 0, whereas\nreturning 0 tells the UDP tunnel layer that the skb was consumed without\nfreeing it. When fou-\u003eprotocol == 0, every packet received on the socket\nreturns 0 from fou_udp_recv() and leaks the sk_buff.\n\nReject FOU_ENCAP_DIRECT when !cfg-\u003eprotocol in fou_create() so that\ncreating a direct encapsulation port without FOU_ATTR_IPPROTO fails with\n-EINVAL while leaving FOU_CMD_DEL and FOU_CMD_GET (which share\nparse_nl_config()) unaffected.\n\nTested in QEMU against Linux 7.3.0-rc3 by sending a FOU_CMD_ADD Generic\nNetlink request with FOU_ATTR_PORT = 5555 and FOU_ATTR_TYPE =\nFOU_ENCAP_DIRECT while omitting FOU_ATTR_IPPROTO. On the unfixed kernel,\nFOU_CMD_ADD succeeds (err = 0), FOU_CMD_GET reports fou-\u003etype = 1 and\nfou-\u003eprotocol = 0, and sending 4000 UDP packets to 127.0.0.1:5555 leaks\nall 4000 sk_buffs (SUnreclaim in /proc/meminfo grows from 41456 kB to\n59008 kB, +17552 kB); with this patch applied, FOU_CMD_ADD is rejected\nwith -EINVAL (-22).",
  "id": "GHSA-rj48-hq74-h6fv",
  "modified": "2026-10-18T18:31:53Z",
  "published": "2026-10-18T18:31:53Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98541"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3bcc1624cc1cdcc05b566475d6e848093ab2a8f6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/46b1ffb7e169c7e401dd890b29e55dbc261f8f01"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/520cf06b8ea0ba5bcc1b8b982ef07f02b5e56221"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7f4ba56f5d310dd018972916167985010a5d66a1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8b43f40798bb2758489fbbcae7e841ad4443c213"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b1229b210ef5a39c58be665e6798203751411842"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d22609f3d13fc5baacd92c222731b03c593401db"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fd20220f86947d66d4dba2d76f13a28dbd86ef30"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



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…

Loading…

Loading…

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.


Loading…