{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53236 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53236 is a high-severity memory corruption vulnerability in Linux kernel, published on 15 Sep 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-53236 and fix it if it is affected.\n\nWhat it is: CVE-2023-53236 is a high-severity memory corruption vulnerability in Linux kernel, published on 15 Sep 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-53236 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-53236/ (Markdown: https://insights.sbomify.com/CVE-2023-53236/index.md)","id":"CVE-2023-53236","markdown":"https://insights.sbomify.com/CVE-2023-53236/index.md","name":"CVE-2023-53236","record":{"aliases":["BELL-CVE-2023-53236","DEBIAN-CVE-2023-53236","GHSA-f667-j8ph-5fg3","UBUNTU-CVE-2023-53236"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A logic error in the Linux kernel iommufd subsystem causes page metadata corruption, potentially leading to system crashes or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\niommufd: Do not corrupt the pfn list when doing batch carry\n\nIf batch-\u003eend is 0 then setting npfns[0] before computing the new value of\npfns will fail to adjust the pfn and result in various page accounting\ncorruptions. It should be ordered after.\n\nThis seems to result in various kinds of page meta-data corruption related\nfailures:\n\n  WARNING: CPU: 1 PID: 527 at mm/gup.c:75 try_grab_folio+0x503/0x740\n  Modules linked in:\n  CPU: 1 PID: 527 Comm: repro Not tainted 6.3.0-rc2-eeac8ede1755+ #1\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n  RIP: 0010:try_grab_folio+0x503/0x740\n  Code: e3 01 48 89 de e8 6d c1 dd ff 48 85 db 0f 84 7c fe ff ff e8 4f bf dd ff 49 8d 47 ff 48 89 45 d0 e9 73 fe ff ff e8 3d bf dd ff \u003c0f\u003e 0b 31 db e9 d0 fc ff ff e8 2f bf dd ff 48 8b 5d c8 31 ff 48 89\n  RSP: 0018:ffffc90000f37908 EFLAGS: 00010046\n  RAX: 0000000000000000 RBX: 00000000fffffc02 RCX: ffffffff81504c26\n  RDX: 0000000000000000 RSI: ffff88800d030000 RDI: 0000000000000002\n  RBP: ffffc90000f37948 R08: 000000000003ca24 R09: 0000000000000008\n  R10: 000000000003ca00 R11: 0000000000000023 R12: ffffea000035d540\n  R13: 0000000000000001 R14: 0000000000000000 R15: ffffea000035d540\n  FS:  00007fecbf659740(0000) GS:ffff88807dd00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 00000000200011c3 CR3: 000000000ef66006 CR4: 0000000000770ee0\n  PKRU: 55555554\n  Call Trace:\n   \u003cTASK\u003e\n   internal_get_user_pages_fast+0xd32/0x2200\n   pin_user_pages_fast+0x65/0x90\n   pfn_reader_user_pin+0x376/0x390\n   pfn_reader_next+0x14a/0x7b0\n   pfn_reader_first+0x140/0x1b0\n   iopt_area_fill_domain+0x74/0x210\n   iopt_table_add_domain+0x30e/0x6e0\n   iommufd_device_selftest_attach+0x7f/0x140\n   iommufd_test+0x10ff/0x16f0\n   iommufd_fops_ioctl+0x206/0x330\n   __x64_sys_ioctl+0x10e/0x160\n   do_syscall_64+0x3b/0x90\n   entry_SYSCALL_64_after_hwframe+0x72/0xdc","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":"iommufd: Do not corrupt the pfn list when doing batch carry","id":"CVE-2023-53236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v11_0_hw_fini","id":"CVE-2023-53237"},"packages":[],"prev":{"headline":"drm/tests: helpers: Avoid a driver uaf","id":"CVE-2023-53235"},"products":["Linux"],"published":"2025-09-15","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-08-05","vendors":["Linux"]},"summary":"A logic error in the Linux kernel iommufd subsystem causes page metadata corruption, potentially leading to system crashes or privilege escalation.","url":"https://insights.sbomify.com/CVE-2023-53236/"}