{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-43247 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-43247 is a medium-severity denial of service vulnerability in Linux kernel, published on 6 May 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-43247 and fix it if it is affected.\n\nWhat it is: CVE-2026-43247 is a medium-severity denial of service vulnerability in Linux kernel, published on 6 May 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-43247 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-2026-43247/ (Markdown: https://insights.sbomify.com/CVE-2026-43247/index.md)","id":"CVE-2026-43247","markdown":"https://insights.sbomify.com/CVE-2026-43247/index.md","name":"CVE-2026-43247","record":{"aliases":["BELL-CVE-2026-43247","DEBIAN-CVE-2026-43247","GHSA-f5wm-6c22-vm3q","UBUNTU-CVE-2026-43247"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A kernel panic occurs in the wave5 media driver when the device enters suspend mode due to an autosuspend timeout, causing a system crash.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: chips-media: wave5: Fix SError of kernel panic when closed\n\nSError of kernel panic rarely happened while testing fluster.\nThe root cause was to enter suspend mode because timeout of autosuspend\ndelay happened.\n\n[   48.834439] SError Interrupt on CPU0, code 0x00000000bf000000 -- SError\n[   48.834455] CPU: 0 UID: 0 PID: 1067 Comm: v4l2h265dec0:sr Not tainted 6.12.9-gc9e21a1ebd75-dirty #7\n[   48.834461] Hardware name: ti Texas Instruments J721S2 EVM/Texas Instruments J721S2 EVM, BIOS 2025.01-00345-gbaf3aaa8ecfa 01/01/2025\n[   48.834464] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   48.834468] pc : wave5_dec_clr_disp_flag+0x40/0x80 [wave5]\n[   48.834488] lr : wave5_dec_clr_disp_flag+0x40/0x80 [wave5]\n[   48.834495] sp : ffff8000856e3a30\n[   48.834497] x29: ffff8000856e3a30 x28: ffff0008093f6010 x27: ffff000809158130\n[   48.834504] x26: 0000000000000000 x25: ffff00080b625000 x24: ffff000804a9ba80\n[   48.834509] x23: ffff000802343028 x22: ffff000809158150 x21: ffff000802218000\n[   48.834513] x20: ffff0008093f6000 x19: ffff0008093f6000 x18: 0000000000000000\n[   48.834518] x17: 0000000000000000 x16: 0000000000000000 x15: 0000ffff74009618\n[   48.834523] x14: 000000010000000c x13: 0000000000000000 x12: 0000000000000000\n[   48.834527] x11: ffffffffffffffff x10: ffffffffffffffff x9 : ffff000802343028\n[   48.834532] x8 : ffff00080b6252a0 x7 : 0000000000000038 x6 : 0000000000000000\n[   48.834536] x5 : ffff00080b625060 x4 : 0000000000000000 x3 : 0000000000000000\n[   48.834541] x2 : 0000000000000000 x1 : ffff800084bf0118 x0 : ffff800084bf0000\n[   48.834547] Kernel panic - not syncing: Asynchronous SError Interrupt\n[   48.834549] CPU: 0 UID: 0 PID: 1067 Comm: v4l2h265dec0:sr Not tainted 6.12.9-gc9e21a1ebd75-dirty #7\n[   48.834554] Hardware name: ti Texas Instruments J721S2 EVM/Texas Instruments J721S2 EVM, BIOS 2025.01-00345-gbaf3aaa8ecfa 01/01/2025\n[   48.834556] Call trace:\n[   48.834559]  dump_backtrace+0x94/0xec\n[   48.834574]  show_stack+0x18/0x24\n[   48.834579]  dump_stack_lvl+0x38/0x90\n[   48.834585]  dump_stack+0x18/0x24\n[   48.834588]  panic+0x35c/0x3e0\n[   48.834592]  nmi_panic+0x40/0x8c\n[   48.834595]  arm64_serror_panic+0x64/0x70\n[   48.834598]  do_serror+0x3c/0x78\n[   48.834601]  el1h_64_error_handler+0x34/0x4c\n[   48.834605]  el1h_64_error+0x64/0x68\n[   48.834608]  wave5_dec_clr_disp_flag+0x40/0x80 [wave5]\n[   48.834615]  wave5_vpu_dec_clr_disp_flag+0x54/0x80 [wave5]\n[   48.834622]  wave5_vpu_dec_buf_queue+0x19c/0x1a0 [wave5]\n[   48.834628]  __enqueue_in_driver+0x3c/0x74 [videobuf2_common]\n[   48.834639]  vb2_core_qbuf+0x508/0x61c [videobuf2_common]\n[   48.834646]  vb2_qbuf+0xa4/0x168 [videobuf2_v4l2]\n[   48.834656]  v4l2_m2m_qbuf+0x80/0x238 [v4l2_mem2mem]\n[   48.834666]  v4l2_m2m_ioctl_qbuf+0x18/0x24 [v4l2_mem2mem]\n[   48.834673]  v4l_qbuf+0x48/0x5c [videodev]\n[   48.834704]  __video_do_ioctl+0x180/0x3f0 [videodev]\n[   48.834725]  video_usercopy+0x2ec/0x68c [videodev]\n[   48.834745]  video_ioctl2+0x18/0x24 [videodev]\n[   48.834766]  v4l2_ioctl+0x40/0x60 [videodev]\n[   48.834786]  __arm64_sys_ioctl+0xa8/0xec\n[   48.834793]  invoke_syscall+0x44/0x100\n[   48.834800]  el0_svc_common.constprop.0+0xc0/0xe0\n[   48.834804]  do_el0_svc+0x1c/0x28\n[   48.834809]  el0_svc+0x30/0xd0\n[   48.834813]  el0t_64_sync_handler+0xc0/0xc4\n[   48.834816]  el0t_64_sync+0x190/0x194\n[   48.834820] SMP: stopping secondary CPUs\n[   48.834831] Kernel Offset: disabled\n[   48.834833] CPU features: 0x08,00002002,80200000,4200421b\n[   48.834837] Memory Limit: none\n[   49.161404] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---","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":"media: chips-media: wave5: Fix SError of kernel panic when closed","id":"CVE-2026-43247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"vhost: move vdpa group bound check to vhost_vdpa","id":"CVE-2026-43248"},"packages":[],"prev":{"headline":"media: i2c/tw9906: Fix potential memory leak in tw9906_probe()","id":"CVE-2026-43246"},"products":["Linux"],"published":"2026-05-06","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A kernel panic occurs in the wave5 media driver when the device enters suspend mode due to an autosuspend timeout, causing a system crash.","url":"https://insights.sbomify.com/CVE-2026-43247/"}