{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99215 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99215 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99215 and fix it if it is affected.\n\nWhat it is: CVE-2026-99215 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99215 in the wild and no public exploit code.\n\nAffected product: Linux. 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-99215/ (Markdown: https://insights.sbomify.com/CVE-2026-99215/index.md)","id":"CVE-2026-99215","markdown":"https://insights.sbomify.com/CVE-2026-99215/index.md","name":"CVE-2026-99215","record":{"aliases":["AZL-111383","BELL-CVE-2026-99215","DEBIAN-CVE-2026-99215","GHSA-5qv3-9727-cwhm","UBUNTU-CVE-2026-99215"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: core: prevent unregistering a power supply while a callback runs\n\nOnce a power supply is registered, its callbacks can immediately start\nfiring from other contexts, such as external_power_changed() triggered by\nthe TCPM stack. If a power supply is unregistered while the callback is\nstill running, the driver data can already be freed when the callback\ntries to access it, leading to a use-after-free.\n\nThis happens e.g. when the hardware bus carrying the power supply device\nmalfunctions (e.g. I2C is hogged down by another malfunctioning device)\nimmediately after the power supply is registered, and thus the core is\nstill processing the callbacks which were queued up when the driver\nstarts the removal, leading in some cases to a kernel crash, e.g.:\n\n[   11.645942] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000005\n[   11.646751] Mem abort info:\n[   11.647006]   ESR = 0x0000000096000004\n[   11.647338]   EC = 0x25: DABT (current EL), IL = 32 bits\n[   11.647806]   SET = 0, FnV = 0\n[   11.648077]   EA = 0, S1PTW = 0\n[   11.648356]   FSC = 0x04: level 0 translation fault\n[   11.648785] Data abort info:\n[   11.649041]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n[   11.649524]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n[   11.649981]   GCS = 0, Overlay = 0, DirtyBit = 0\n[   11.650390] [0000000000000005] user address but active_mm is swapper\n[   11.650955] Internal error: Oops: 0000000096000004 [#1]  SMP\n[   11.651460] Modules linked in:\n[   11.651742] CPU: 1 UID: 0 PID: 144 Comm: kworker/1:2 Not tainted 7.2.0-rc6-g62a9297af2cd #1 PREEMPT\n[   11.652553] Hardware name: Flipper One rev. F0B1C2 (DT)\n[   11.653024] Workqueue: events power_supply_changed_work\n[   11.653511] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   11.654135] pc : __power_supply_is_supplied_by+0x18/0x100\n[   11.654624] lr : __power_supply_am_i_supplied+0x40/0xb8\n[   11.655098] sp : ffff80008192bb30\n[   11.655399] x29: ffff80008192bb30 x28: 0000000000000000 x27: 0000000000000000\n[   11.656049] x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000\n[   11.656695] x23: ffff0000c19f4200 x22: ffffdb2232ba4ea8 x21: ffff80008192bc28\n[   11.657344] x20: ffff0000c1eef000 x19: ffff80008192bc18 x18: 00000000a0886e62\n[   11.657991] x17: 000000040044ffff x16: 04500072b5503510 x15: 0000000000000000\n[   11.658639] x14: 0000000000000000 x13: 0000000000000220 x12: 0000000000000000\n[   11.659286] x11: 0000000000000000 x10: ffff0000c1fdb2b0 x9 : ffffdb2232ba5590\n[   11.659934] x8 : 00000000e5b906e6 x7 : ffff0000c2502778 x6 : ffffdb22339793d0\n[   11.660581] x5 : ffff80008192bc18 x4 : ffff0000c19cbca0 x3 : 0000000000000000\n[   11.661228] x2 : ffff0000c1fdaf40 x1 : ffffffffffffffed x0 : ffff0000c1eef000\n[   11.661878] Call trace:\n[   11.662103]  __power_supply_is_supplied_by+0x18/0x100 (P)\n[   11.662596]  __power_supply_am_i_supplied+0x40/0xb8\n[   11.663040]  psy_for_each_psy_cb+0x20/0x40\n[   11.663416]  class_for_each_device+0x110/0x150\n[   11.663825]  power_supply_am_i_supplied+0x68/0x100\n[   11.664262]  bq257xx_external_power_changed+0x58/0x140\n[   11.664733]  __power_supply_changed_work+0x60/0x80\n[   11.665170]  psy_for_each_psy_cb+0x20/0x40\n[   11.665545]  class_for_each_device+0x110/0x150\n[   11.665953]  power_supply_changed_work+0x98/0x1b8\n[   11.666382]  process_one_work+0x164/0x4c0\n[   11.666758]  worker_thread+0x19c/0x320\n[   11.667104]  kthread+0x138/0x150\n[   11.667408]  ret_from_fork+0x10/0x20\n[   11.667744] Code: d503233f a9bd7bfd 910003fd a90153f3 (f9400c34)\n[   11.668294] ---[ end trace 0000000000000000 ]---\n\nAdd a read-write semaphore between external_power_changed() and\npower_supply_unregister() to prevent the latter from returning (and thus\nthe driver from freeing its data) while the callback is still running.","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":"power: supply: core: prevent unregistering a power supply while a callback runs","id":"CVE-2026-99215","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Drivers: hv: Don't reset VMBus connection state on error/exit paths","id":"CVE-2026-99216"},"packages":[],"prev":{"headline":"drm/vc4: hdmi: Move packet RAM enable to PM runtime","id":"CVE-2026-99214"},"products":["Linux"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99215/"}