{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98541 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98541 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98541 and fix it if it is affected.\n\nWhat it is: CVE-2026-98541 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98541 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98541/ (Markdown: https://insights.sbomify.com/CVE-2026-98541/index.md)","id":"CVE-2026-98541","markdown":"https://insights.sbomify.com/CVE-2026-98541/index.md","name":"CVE-2026-98541","record":{"aliases":["AZL-109124","BELL-CVE-2026-98541","DEBIAN-CVE-2026-98541","GHSA-rj48-hq74-h6fv","UBUNTU-CVE-2026-98541"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local attacker with high privileges can cause a memory leak in the Linux kernel's FOU module by omitting a protocol attribute, leading to denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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't 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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"fou: reject omitted FOU_ATTR_IPPROTO on FOU_ENCAP_DIRECT","id":"CVE-2026-98541","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"cgroup/cpuset: Return PERR_NOCPUS in remote_partition_enable() on subpartitions_cpus conflict","id":"CVE-2026-98542"},"packages":[],"prev":{"headline":"fprobe: Terminate the fgraph_data list when the reservation is not filled","id":"CVE-2026-98540"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker with high privileges can cause a memory leak in the Linux kernel's FOU module by omitting a protocol attribute, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-98541/"}