{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-21845 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-21845 is a medium-severity denial of service vulnerability in Linux kernel, published on 12 Mar 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-2025-21845 and fix it if it is affected.\n\nWhat it is: CVE-2025-21845 is a medium-severity denial of service vulnerability in Linux kernel, published on 12 Mar 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-2025-21845 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-2025-21845/ (Markdown: https://insights.sbomify.com/CVE-2025-21845/index.md)","id":"CVE-2025-21845","markdown":"https://insights.sbomify.com/CVE-2025-21845/index.md","name":"CVE-2025-21845","record":{"aliases":["BELL-CVE-2025-21845","DEBIAN-CVE-2025-21845","GHSA-263p-9rp6-x92j","UBUNTU-CVE-2025-21845"],"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 bug in the Linux kernel's SST SPI-NOR driver causes a kernel crash during write operations, leading to denial of service.","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":"cisa-adp","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\nmtd: spi-nor: sst: Fix SST write failure\n\n'commit 18bcb4aa54ea (\"mtd: spi-nor: sst: Factor out common write operation\nto `sst_nor_write_data()`\")' introduced a bug where only one byte of data\nis written, regardless of the number of bytes passed to\nsst_nor_write_data(), causing a kernel crash during the write operation.\nEnsure the correct number of bytes are written as passed to\nsst_nor_write_data().\n\nCall trace:\n[   57.400180] ------------[ cut here ]------------\n[   57.404842] While writing 2 byte written 1 bytes\n[   57.409493] WARNING: CPU: 0 PID: 737 at drivers/mtd/spi-nor/sst.c:187 sst_nor_write_data+0x6c/0x74\n[   57.418464] Modules linked in:\n[   57.421517] CPU: 0 UID: 0 PID: 737 Comm: mtd_debug Not tainted 6.12.0-g5ad04afd91f9 #30\n[   57.429517] Hardware name: Xilinx Versal A2197 Processor board revA - x-prc-02 revA (DT)\n[   57.437600] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   57.444557] pc : sst_nor_write_data+0x6c/0x74\n[   57.448911] lr : sst_nor_write_data+0x6c/0x74\n[   57.453264] sp : ffff80008232bb40\n[   57.456570] x29: ffff80008232bb40 x28: 0000000000010000 x27: 0000000000000001\n[   57.463708] x26: 000000000000ffff x25: 0000000000000000 x24: 0000000000000000\n[   57.470843] x23: 0000000000010000 x22: ffff80008232bbf0 x21: ffff000816230000\n[   57.477978] x20: ffff0008056c0080 x19: 0000000000000002 x18: 0000000000000006\n[   57.485112] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80008232b580\n[   57.492246] x14: 0000000000000000 x13: ffff8000816d1530 x12: 00000000000004a4\n[   57.499380] x11: 000000000000018c x10: ffff8000816fd530 x9 : ffff8000816d1530\n[   57.506515] x8 : 00000000fffff7ff x7 : ffff8000816fd530 x6 : 0000000000000001\n[   57.513649] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000\n[   57.520782] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0008049b0000\n[   57.527916] Call trace:\n[   57.530354]  sst_nor_write_data+0x6c/0x74\n[   57.534361]  sst_nor_write+0xb4/0x18c\n[   57.538019]  mtd_write_oob_std+0x7c/0x88\n[   57.541941]  mtd_write_oob+0x70/0xbc\n[   57.545511]  mtd_write+0x68/0xa8\n[   57.548733]  mtdchar_write+0x10c/0x290\n[   57.552477]  vfs_write+0xb4/0x3a8\n[   57.555791]  ksys_write+0x74/0x10c\n[   57.559189]  __arm64_sys_write+0x1c/0x28\n[   57.563109]  invoke_syscall+0x54/0x11c\n[   57.566856]  el0_svc_common.constprop.0+0xc0/0xe0\n[   57.571557]  do_el0_svc+0x1c/0x28\n[   57.574868]  el0_svc+0x30/0xcc\n[   57.577921]  el0t_64_sync_handler+0x120/0x12c\n[   57.582276]  el0t_64_sync+0x190/0x194\n[   57.585933] ---[ end trace 0000000000000000 ]---\n\n[pratyush@kernel.org: add Cc stable tag]","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":"mtd: spi-nor: sst: Fix SST write failure","id":"CVE-2025-21845","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"acct: perform last write from workqueue","id":"CVE-2025-21846"},"packages":[],"prev":{"headline":"smb: client: Add check for next_buffer in receive_encrypted_standard()","id":"CVE-2025-21844"},"products":["Linux"],"published":"2025-03-12","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":"partial"},"state":"PUBLISHED","updated":"2026-06-01","vendors":["Linux"]},"summary":"A bug in the Linux kernel's SST SPI-NOR driver causes a kernel crash during write operations, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-21845/"}