{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-23166 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23166 is a medium-severity vulnerability in Linux kernel, published on 14 Feb 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-23166 and fix it if it is affected.\n\nWhat it is: CVE-2026-23166 is a medium-severity vulnerability in Linux kernel, published on 14 Feb 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-23166 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-23166/ (Markdown: https://insights.sbomify.com/CVE-2026-23166/index.md)","id":"CVE-2026-23166","markdown":"https://insights.sbomify.com/CVE-2026-23166/index.md","name":"CVE-2026-23166","record":{"aliases":["BELL-CVE-2026-23166","DEBIAN-CVE-2026-23166","GHSA-5p9c-24w4-pq6q","ROOT-OS-UBUNTU-2404-CVE-2026-23166","UBUNTU-CVE-2026-23166"],"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 NULL pointer dereference in the Intel ice network driver causes a kernel crash during system resume, leading to denial of service.","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":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-476","name":"NULL Pointer Dereference"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nice: Fix NULL pointer dereference in ice_vsi_set_napi_queues\n\nAdd NULL pointer checks in ice_vsi_set_napi_queues() to prevent crashes\nduring resume from suspend when rings[q_idx]-\u003eq_vector is NULL.\n\nTested adaptor:\n60:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller E810-XXV for SFP [8086:159b] (rev 02)\n        Subsystem: Intel Corporation Ethernet Network Adapter E810-XXV-2 [8086:4003]\n\nSR-IOV state: both disabled and enabled can reproduce this issue.\n\nkernel version: v6.18\n\nReproduce steps:\nBoot up and execute suspend like systemctl suspend or rtcwake.\n\nLog:\n\u003c1\u003e[  231.443607] BUG: kernel NULL pointer dereference, address: 0000000000000040\n\u003c1\u003e[  231.444052] #PF: supervisor read access in kernel mode\n\u003c1\u003e[  231.444484] #PF: error_code(0x0000) - not-present page\n\u003c6\u003e[  231.444913] PGD 0 P4D 0\n\u003c4\u003e[  231.445342] Oops: Oops: 0000 [#1] SMP NOPTI\n\u003c4\u003e[  231.446635] RIP: 0010:netif_queue_set_napi+0xa/0x170\n\u003c4\u003e[  231.447067] Code: 31 f6 31 ff c3 cc cc cc cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 48 85 c9 74 0b \u003c48\u003e 83 79 30 00 0f 84 39 01 00 00 55 41 89 d1 49 89 f8 89 f2 48 89\n\u003c4\u003e[  231.447513] RSP: 0018:ffffcc780fc078c0 EFLAGS: 00010202\n\u003c4\u003e[  231.447961] RAX: ffff8b848ca30400 RBX: ffff8b848caf2028 RCX: 0000000000000010\n\u003c4\u003e[  231.448443] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff8b848dbd4000\n\u003c4\u003e[  231.448896] RBP: ffffcc780fc078e8 R08: 0000000000000000 R09: 0000000000000000\n\u003c4\u003e[  231.449345] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001\n\u003c4\u003e[  231.449817] R13: ffff8b848dbd4000 R14: ffff8b84833390c8 R15: 0000000000000000\n\u003c4\u003e[  231.450265] FS:  00007c7b29e9d740(0000) GS:ffff8b8c068e2000(0000) knlGS:0000000000000000\n\u003c4\u003e[  231.450715] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n\u003c4\u003e[  231.451179] CR2: 0000000000000040 CR3: 000000030626f004 CR4: 0000000000f72ef0\n\u003c4\u003e[  231.451629] PKRU: 55555554\n\u003c4\u003e[  231.452076] Call Trace:\n\u003c4\u003e[  231.452549]  \u003cTASK\u003e\n\u003c4\u003e[  231.452996]  ? ice_vsi_set_napi_queues+0x4d/0x110 [ice]\n\u003c4\u003e[  231.453482]  ice_resume+0xfd/0x220 [ice]\n\u003c4\u003e[  231.453977]  ? __pfx_pci_pm_resume+0x10/0x10\n\u003c4\u003e[  231.454425]  pci_pm_resume+0x8c/0x140\n\u003c4\u003e[  231.454872]  ? __pfx_pci_pm_resume+0x10/0x10\n\u003c4\u003e[  231.455347]  dpm_run_callback+0x5f/0x160\n\u003c4\u003e[  231.455796]  ? dpm_wait_for_superior+0x107/0x170\n\u003c4\u003e[  231.456244]  device_resume+0x177/0x270\n\u003c4\u003e[  231.456708]  dpm_resume+0x209/0x2f0\n\u003c4\u003e[  231.457151]  dpm_resume_end+0x15/0x30\n\u003c4\u003e[  231.457596]  suspend_devices_and_enter+0x1da/0x2b0\n\u003c4\u003e[  231.458054]  enter_state+0x10e/0x570\n\nAdd defensive checks for both the ring pointer and its q_vector\nbefore dereferencing, allowing the system to resume successfully even when\nq_vectors are unmapped.","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":"ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues","id":"CVE-2026-23166","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"nfc: nci: Fix race between rfkill and nci_unregister_device().","id":"CVE-2026-23167"},"packages":[],"prev":{"headline":"sfc: fix deadlock in RSS config read","id":"CVE-2026-23165"},"products":["Linux"],"published":"2026-02-14","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-23","vendors":["Linux"]},"summary":"A NULL pointer dereference in the Intel ice network driver causes a kernel crash during system resume, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-23166/"}