{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53086 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53086 is a high-severity vulnerability in Linux kernel, published on 2 May 2025. 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-2023-53086 and fix it if it is affected.\n\nWhat it is: CVE-2023-53086 is a high-severity vulnerability in Linux kernel, published on 2 May 2025. 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-2023-53086 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-2023-53086/ (Markdown: https://insights.sbomify.com/CVE-2023-53086/index.md)","id":"CVE-2023-53086","markdown":"https://insights.sbomify.com/CVE-2023-53086/index.md","name":"CVE-2023-53086","record":{"aliases":["BELL-CVE-2023-53086","DEBIAN-CVE-2023-53086","GHSA-j2jx-2q7v-qq3w","UBUNTU-CVE-2023-53086"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel WiFi driver","requires_auth":"none","summary":"A missing check for non-mmio devices in the mt76 WiFi driver causes a kernel crash when WED status is incorrectly accessed.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: connac: do not check WED status for non-mmio devices\n\nWED is supported just for mmio devices, so do not check it for usb or\nsdio devices. This patch fixes the crash reported below:\n\n[   21.946627] wlp0s3u1i3: authenticate with c4:41:1e:f5:2b:1d\n[   22.525298] wlp0s3u1i3: send auth to c4:41:1e:f5:2b:1d (try 1/3)\n[   22.548274] wlp0s3u1i3: authenticate with c4:41:1e:f5:2b:1d\n[   22.557694] wlp0s3u1i3: send auth to c4:41:1e:f5:2b:1d (try 1/3)\n[   22.565885] wlp0s3u1i3: authenticated\n[   22.569502] wlp0s3u1i3: associate with c4:41:1e:f5:2b:1d (try 1/3)\n[   22.578966] wlp0s3u1i3: RX AssocResp from c4:41:1e:f5:2b:1d (capab=0x11 status=30 aid=3)\n[   22.579113] wlp0s3u1i3: c4:41:1e:f5:2b:1d rejected association temporarily; comeback duration 1000 TU (1024 ms)\n[   23.649518] wlp0s3u1i3: associate with c4:41:1e:f5:2b:1d (try 2/3)\n[   23.752528] wlp0s3u1i3: RX AssocResp from c4:41:1e:f5:2b:1d (capab=0x11 status=0 aid=3)\n[   23.797450] wlp0s3u1i3: associated\n[   24.959527] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)\n[   24.959640] BUG: unable to handle page fault for address: ffff88800c223200\n[   24.959706] #PF: supervisor instruction fetch in kernel mode\n[   24.959788] #PF: error_code(0x0011) - permissions violation\n[   24.959846] PGD 2c01067 P4D 2c01067 PUD 2c02067 PMD c2a8063 PTE 800000000c223163\n[   24.959957] Oops: 0011 [#1] PREEMPT SMP\n[   24.960009] CPU: 0 PID: 391 Comm: wpa_supplicant Not tainted 6.2.0-kvm #18\n[   24.960089] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.1-2.fc37 04/01/2014\n[   24.960191] RIP: 0010:0xffff88800c223200\n[   24.960446] RSP: 0018:ffffc90000ff7698 EFLAGS: 00010282\n[   24.960513] RAX: ffff888028397010 RBX: ffff88800c26e630 RCX: 0000000000000058\n[   24.960598] RDX: ffff88800c26f844 RSI: 0000000000000006 RDI: ffff888028397010\n[   24.960682] RBP: ffff88800ea72f00 R08: 18b873fbab2b964c R09: be06b38235f3c63c\n[   24.960766] R10: 18b873fbab2b964c R11: be06b38235f3c63c R12: 0000000000000001\n[   24.960853] R13: ffff88800c26f84c R14: ffff8880063f0ff8 R15: ffff88800c26e644\n[   24.960950] FS:  00007effcea327c0(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000\n[   24.961036] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   24.961106] CR2: ffff88800c223200 CR3: 000000000eaa2000 CR4: 00000000000006b0\n[   24.961190] Call Trace:\n[   24.961219]  \u003cTASK\u003e\n[   24.961245]  ? mt76_connac_mcu_add_key+0x2cf/0x310\n[   24.961313]  ? mt7921_set_key+0x150/0x200\n[   24.961365]  ? drv_set_key+0xa9/0x1b0\n[   24.961418]  ? ieee80211_key_enable_hw_accel+0xd9/0x240\n[   24.961485]  ? ieee80211_key_replace+0x3f3/0x730\n[   24.961541]  ? crypto_shash_setkey+0x89/0xd0\n[   24.961597]  ? ieee80211_key_link+0x2d7/0x3a0\n[   24.961664]  ? crypto_aead_setauthsize+0x31/0x50\n[   24.961730]  ? sta_info_hash_lookup+0xa6/0xf0\n[   24.961785]  ? ieee80211_add_key+0x1fc/0x250\n[   24.961842]  ? rdev_add_key+0x41/0x140\n[   24.961882]  ? nl80211_parse_key+0x6c/0x2f0\n[   24.961940]  ? nl80211_new_key+0x24a/0x290\n[   24.961984]  ? genl_rcv_msg+0x36c/0x3a0\n[   24.962036]  ? rdev_mod_link_station+0xe0/0xe0\n[   24.962102]  ? nl80211_set_key+0x410/0x410\n[   24.962143]  ? nl80211_pre_doit+0x200/0x200\n[   24.962187]  ? genl_bind+0xc0/0xc0\n[   24.962217]  ? netlink_rcv_skb+0xaa/0xd0\n[   24.962259]  ? genl_rcv+0x24/0x40\n[   24.962300]  ? netlink_unicast+0x224/0x2f0\n[   24.962345]  ? netlink_sendmsg+0x30b/0x3d0\n[   24.962388]  ? ____sys_sendmsg+0x109/0x1b0\n[   24.962388]  ? ____sys_sendmsg+0x109/0x1b0\n[   24.962440]  ? __import_iovec+0x2e/0x110\n[   24.962482]  ? ___sys_sendmsg+0xbe/0xe0\n[   24.962525]  ? mod_objcg_state+0x25c/0x330\n[   24.962576]  ? __dentry_kill+0x19e/0x1d0\n[   24.962618]  ? call_rcu+0x18f/0x270\n[   24.962660]  ? __dentry_kill+0x19e/0x1d0\n[   24.962702]  ? __x64_sys_sendmsg+0x70/0x90\n[   24.962744]  ? do_syscall_64+0x3d/0x80\n[   24.962796]  ? exit_to_user_mode_prepare+0x1b/0x70\n[   24.962852]  ? entry_SYSCA\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":"wifi: mt76: connac: do not check WED status for non-mmio devices","id":"CVE-2023-53086","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"drm/i915/active: Fix misuse of non-idle barriers as fence trackers","id":"CVE-2023-53087"},"packages":[],"prev":{"headline":"drm/edid: fix info leak when failing to get panel id","id":"CVE-2023-53085"},"products":["Linux"],"published":"2025-05-02","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Linux"]},"summary":"A missing check for non-mmio devices in the mt76 WiFi driver causes a kernel crash when WED status is incorrectly accessed.","url":"https://insights.sbomify.com/CVE-2023-53086/"}