{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-46956 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2021-46956 is a medium-severity memory corruption vulnerability in Linux kernel, published on 27 Feb 2024. 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-2021-46956 and fix it if it is affected.\n\nWhat it is: CVE-2021-46956 is a medium-severity memory corruption vulnerability in Linux kernel, published on 27 Feb 2024. 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-2021-46956 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-2021-46956/ (Markdown: https://insights.sbomify.com/CVE-2021-46956/index.md)","id":"CVE-2021-46956","markdown":"https://insights.sbomify.com/CVE-2021-46956/index.md","name":"CVE-2021-46956","record":{"aliases":["DEBIAN-CVE-2021-46956","GHSA-7r25-m49h-vw58","UBUNTU-CVE-2021-46956"],"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":"low_privilege","summary":"A memory leak in the Linux kernel virtiofs driver can lead to resource exhaustion and denial of service when duplicate tags are passed.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirtiofs: fix memory leak in virtio_fs_probe()\n\nWhen accidentally passing twice the same tag to qemu, kmemleak ended up\nreporting a memory leak in virtiofs.  Also, looking at the log I saw the\nfollowing error (that's when I realised the duplicated tag):\n\n  virtiofs: probe of virtio5 failed with error -17\n\nHere's the kmemleak log for reference:\n\nunreferenced object 0xffff888103d47800 (size 1024):\n  comm \"systemd-udevd\", pid 118, jiffies 4294893780 (age 18.340s)\n  hex dump (first 32 bytes):\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n    ff ff ff ff ff ff ff ff 80 90 02 a0 ff ff ff ff  ................\n  backtrace:\n    [\u003c000000000ebb87c1\u003e] virtio_fs_probe+0x171/0x7ae [virtiofs]\n    [\u003c00000000f8aca419\u003e] virtio_dev_probe+0x15f/0x210\n    [\u003c000000004d6baf3c\u003e] really_probe+0xea/0x430\n    [\u003c00000000a6ceeac8\u003e] device_driver_attach+0xa8/0xb0\n    [\u003c00000000196f47a7\u003e] __driver_attach+0x98/0x140\n    [\u003c000000000b20601d\u003e] bus_for_each_dev+0x7b/0xc0\n    [\u003c00000000399c7b7f\u003e] bus_add_driver+0x11b/0x1f0\n    [\u003c0000000032b09ba7\u003e] driver_register+0x8f/0xe0\n    [\u003c00000000cdd55998\u003e] 0xffffffffa002c013\n    [\u003c000000000ea196a2\u003e] do_one_initcall+0x64/0x2e0\n    [\u003c0000000008f727ce\u003e] do_init_module+0x5c/0x260\n    [\u003c000000003cdedab6\u003e] __do_sys_finit_module+0xb5/0x120\n    [\u003c00000000ad2f48c6\u003e] do_syscall_64+0x33/0x40\n    [\u003c00000000809526b5\u003e] entry_SYSCALL_64_after_hwframe+0x44/0xae","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":"virtiofs: fix memory leak in virtio_fs_probe()","id":"CVE-2021-46956","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":5,"next":{"headline":"riscv/kprobe: fix kernel panic when invoking sys_read traced by kprobe","id":"CVE-2021-46957"},"packages":[],"prev":{"headline":"openvswitch: fix stack OOB read while fragmenting IPv4 packets","id":"CVE-2021-46955"},"products":["Linux"],"published":"2024-02-27","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel virtiofs driver can lead to resource exhaustion and denial of service when duplicate tags are passed.","url":"https://insights.sbomify.com/CVE-2021-46956/"}