{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-47300 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2021-47300 is a high-severity memory corruption vulnerability in Linux kernel, published on 21 May 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-47300 and fix it if it is affected.\n\nWhat it is: CVE-2021-47300 is a high-severity memory corruption vulnerability in Linux kernel, published on 21 May 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-47300 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-47300/ (Markdown: https://insights.sbomify.com/CVE-2021-47300/index.md)","id":"CVE-2021-47300","markdown":"https://insights.sbomify.com/CVE-2021-47300/index.md","name":"CVE-2021-47300","record":{"aliases":["DEBIAN-CVE-2021-47300","GHSA-w5h4-c4xx-3r8p","UBUNTU-CVE-2021-47300"],"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 flaw in the Linux kernel BPF interpreter causes a slab-out-of-bounds read when JIT compilation fails, leading to a system crash.","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":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix tail_call_reachable rejection for interpreter when jit failed\n\nDuring testing of f263a81451c1 (\"bpf: Track subprog poke descriptors correctly\nand fix use-after-free\") under various failure conditions, for example, when\njit_subprogs() fails and tries to clean up the program to be run under the\ninterpreter, we ran into the following freeze:\n\n  [...]\n  #127/8 tailcall_bpf2bpf_3:FAIL\n  [...]\n  [   92.041251] BUG: KASAN: slab-out-of-bounds in ___bpf_prog_run+0x1b9d/0x2e20\n  [   92.042408] Read of size 8 at addr ffff88800da67f68 by task test_progs/682\n  [   92.043707]\n  [   92.044030] CPU: 1 PID: 682 Comm: test_progs Tainted: G   O   5.13.0-53301-ge6c08cb33a30-dirty #87\n  [   92.045542] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014\n  [   92.046785] Call Trace:\n  [   92.047171]  ? __bpf_prog_run_args64+0xc0/0xc0\n  [   92.047773]  ? __bpf_prog_run_args32+0x8b/0xb0\n  [   92.048389]  ? __bpf_prog_run_args64+0xc0/0xc0\n  [   92.049019]  ? ktime_get+0x117/0x130\n  [...] // few hundred [similar] lines more\n  [   92.659025]  ? ktime_get+0x117/0x130\n  [   92.659845]  ? __bpf_prog_run_args64+0xc0/0xc0\n  [   92.660738]  ? __bpf_prog_run_args32+0x8b/0xb0\n  [   92.661528]  ? __bpf_prog_run_args64+0xc0/0xc0\n  [   92.662378]  ? print_usage_bug+0x50/0x50\n  [   92.663221]  ? print_usage_bug+0x50/0x50\n  [   92.664077]  ? bpf_ksym_find+0x9c/0xe0\n  [   92.664887]  ? ktime_get+0x117/0x130\n  [   92.665624]  ? kernel_text_address+0xf5/0x100\n  [   92.666529]  ? __kernel_text_address+0xe/0x30\n  [   92.667725]  ? unwind_get_return_address+0x2f/0x50\n  [   92.668854]  ? ___bpf_prog_run+0x15d4/0x2e20\n  [   92.670185]  ? ktime_get+0x117/0x130\n  [   92.671130]  ? __bpf_prog_run_args64+0xc0/0xc0\n  [   92.672020]  ? __bpf_prog_run_args32+0x8b/0xb0\n  [   92.672860]  ? __bpf_prog_run_args64+0xc0/0xc0\n  [   92.675159]  ? ktime_get+0x117/0x130\n  [   92.677074]  ? lock_is_held_type+0xd5/0x130\n  [   92.678662]  ? ___bpf_prog_run+0x15d4/0x2e20\n  [   92.680046]  ? ktime_get+0x117/0x130\n  [   92.681285]  ? __bpf_prog_run32+0x6b/0x90\n  [   92.682601]  ? __bpf_prog_run64+0x90/0x90\n  [   92.683636]  ? lock_downgrade+0x370/0x370\n  [   92.684647]  ? mark_held_locks+0x44/0x90\n  [   92.685652]  ? ktime_get+0x117/0x130\n  [   92.686752]  ? lockdep_hardirqs_on+0x79/0x100\n  [   92.688004]  ? ktime_get+0x117/0x130\n  [   92.688573]  ? __cant_migrate+0x2b/0x80\n  [   92.689192]  ? bpf_test_run+0x2f4/0x510\n  [   92.689869]  ? bpf_test_timer_continue+0x1c0/0x1c0\n  [   92.690856]  ? rcu_read_lock_bh_held+0x90/0x90\n  [   92.691506]  ? __kasan_slab_alloc+0x61/0x80\n  [   92.692128]  ? eth_type_trans+0x128/0x240\n  [   92.692737]  ? __build_skb+0x46/0x50\n  [   92.693252]  ? bpf_prog_test_run_skb+0x65e/0xc50\n  [   92.693954]  ? bpf_prog_test_run_raw_tp+0x2d0/0x2d0\n  [   92.694639]  ? __fget_light+0xa1/0x100\n  [   92.695162]  ? bpf_prog_inc+0x23/0x30\n  [   92.695685]  ? __sys_bpf+0xb40/0x2c80\n  [   92.696324]  ? bpf_link_get_from_fd+0x90/0x90\n  [   92.697150]  ? mark_held_locks+0x24/0x90\n  [   92.698007]  ? lockdep_hardirqs_on_prepare+0x124/0x220\n  [   92.699045]  ? finish_task_switch+0xe6/0x370\n  [   92.700072]  ? lockdep_hardirqs_on+0x79/0x100\n  [   92.701233]  ? finish_task_switch+0x11d/0x370\n  [   92.702264]  ? __switch_to+0x2c0/0x740\n  [   92.703148]  ? mark_held_locks+0x24/0x90\n  [   92.704155]  ? __x64_sys_bpf+0x45/0x50\n  [   92.705146]  ? do_syscall_64+0x35/0x80\n  [   92.706953]  ? entry_SYSCALL_64_after_hwframe+0x44/0xae\n  [...]\n\nTurns out that the program rejection from e411901c0b77 (\"bpf: allow for tailcalls\nin BPF subprograms for x64 JIT\") is buggy since env-\u003eprog-\u003eaux-\u003etail_call_reachable\nis never true. Commit ebf7d1f508a7 (\"bpf, x64: rework pro/epilogue and tailcall\nhandling in JIT\") added a tracker into check_max_stack_depth() which propagates\nthe tail_call_reachable condition throughout the subprograms. This info is then\nassigned to the subprogram's \n---truncated---","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":"bpf: Fix tail_call_reachable rejection for interpreter when jit failed","id":"CVE-2021-47300","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":3,"next":{"headline":"igb: Fix use-after-free error during reset","id":"CVE-2021-47301"},"packages":[],"prev":{"headline":"xdp, net: Fix use-after-free in bpf_xdp_link_release","id":"CVE-2021-47299"},"products":["Linux"],"published":"2024-05-21","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-08-05","vendors":["Linux"]},"summary":"A flaw in the Linux kernel BPF interpreter causes a slab-out-of-bounds read when JIT compilation fails, leading to a system crash.","url":"https://insights.sbomify.com/CVE-2021-47300/"}