{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-53584 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53584 is a medium-severity denial of service vulnerability in Linux kernel, published on 4 Oct 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-53584 and fix it if it is affected.\n\nWhat it is: CVE-2023-53584 is a medium-severity denial of service vulnerability in Linux kernel, published on 4 Oct 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-53584 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-53584/ (Markdown: https://insights.sbomify.com/CVE-2023-53584/index.md)","id":"CVE-2023-53584","markdown":"https://insights.sbomify.com/CVE-2023-53584/index.md","name":"CVE-2023-53584","record":{"aliases":["BELL-CVE-2023-53584","DEBIAN-CVE-2023-53584","GHSA-r29j-x5gx-p5gg","ROOT-OS-DEBIAN-11-CVE-2023-53584","ROOT-OS-UBUNTU-2204-CVE-2023-53584","UBUNTU-CVE-2023-53584"],"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 race condition in the Linux kernel UBIFS filesystem triggers an assertion failure, causing the filesystem to switch to read-only mode and resulting in a 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":"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-617","name":"Reachable Assertion"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process\n\nThere are two states for ubifs writing pages:\n1. Dirty, Private\n2. Not Dirty, Not Private\n\nThe normal process cannot go to ubifs_releasepage() which means there\nexists pages being private but not dirty. Reproducer[1] shows that it\ncould occur (which maybe related to [2]) with following process:\n\n     PA                     PB                    PC\nlock(page)[PA]\nubifs_write_end\n  attach_page_private         // set Private\n  __set_page_dirty_nobuffers  // set Dirty\nunlock(page)\n\nwrite_cache_pages[PA]\n  lock(page)\n  clear_page_dirty_for_io(page)\t// clear Dirty\n  ubifs_writepage\n\n                        do_truncation[PB]\n\t\t\t  truncate_setsize\n\t\t\t    i_size_write(inode, newsize) // newsize = 0\n\n    i_size = i_size_read(inode)\t// i_size = 0\n    end_index = i_size \u003e\u003e PAGE_SHIFT\n    if (page-\u003eindex \u003e end_index)\n      goto out // jump\nout:\nunlock(page)   // Private, Not Dirty\n\n\t\t\t\t\t\tgeneric_fadvise[PC]\n\t\t\t\t\t\t  lock(page)\n\t\t\t\t\t\t  invalidate_inode_page\n\t\t\t\t\t\t    try_to_release_page\n\t\t\t\t\t\t      ubifs_releasepage\n\t\t\t\t\t\t        ubifs_assert(c, 0)\n\t\t                                        // bad assertion!\n\t\t\t\t\t\t  unlock(page)\n\t\t\t  truncate_pagecache[PB]\n\nThen we may get following assertion failed:\n  UBIFS error (ubi0:0 pid 1683): ubifs_assert_failed [ubifs]:\n  UBIFS assert failed: 0, in fs/ubifs/file.c:1513\n  UBIFS warning (ubi0:0 pid 1683): ubifs_ro_mode [ubifs]:\n  switched to read-only mode, error -22\n  CPU: 2 PID: 1683 Comm: aa Not tainted 5.16.0-rc5-00184-g0bca5994cacc-dirty #308\n  Call Trace:\n    dump_stack+0x13/0x1b\n    ubifs_ro_mode+0x54/0x60 [ubifs]\n    ubifs_assert_failed+0x4b/0x80 [ubifs]\n    ubifs_releasepage+0x67/0x1d0 [ubifs]\n    try_to_release_page+0x57/0xe0\n    invalidate_inode_page+0xfb/0x130\n    __invalidate_mapping_pages+0xb9/0x280\n    invalidate_mapping_pagevec+0x12/0x20\n    generic_fadvise+0x303/0x3c0\n    ksys_fadvise64_64+0x4c/0xb0\n\n[1] https://bugzilla.kernel.org/show_bug.cgi?id=215373\n[2] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirty","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":"ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process","id":"CVE-2023-53584","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"bpf: reject unhashed sockets in bpf_sk_assign","id":"CVE-2023-53585"},"packages":[],"prev":{"headline":"perf: RISC-V: Remove PERF_HES_STOPPED flag checking in riscv_pmu_start()","id":"CVE-2023-53583"},"products":["Linux"],"published":"2025-10-04","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-11","vendors":["Linux"]},"summary":"A race condition in the Linux kernel UBIFS filesystem triggers an assertion failure, causing the filesystem to switch to read-only mode and resulting in a denial of service.","url":"https://insights.sbomify.com/CVE-2023-53584/"}