{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-57895 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-57895 is a high-severity vulnerability in Linux kernel, published on 15 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-57895 and fix it if it is affected.\n\nWhat it is: CVE-2024-57895 is a high-severity vulnerability in Linux kernel, published on 15 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-57895 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-2024-57895/ (Markdown: https://insights.sbomify.com/CVE-2024-57895/index.md)","id":"CVE-2024-57895","markdown":"https://insights.sbomify.com/CVE-2024-57895/index.md","name":"CVE-2024-57895","record":{"aliases":["AZL-55823","AZL-55881","BELL-CVE-2024-57895","DEBIAN-CVE-2024-57895","GHSA-gvh3-4cff-qfpj","ROOT-OS-DEBIAN-12-CVE-2024-57895","ROOT-OS-UBUNTU-2204-CVE-2024-57895","UBUNTU-CVE-2024-57895"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel SMB server","requires_auth":"low_privilege","summary":"A missing flag in the ksmbd kernel module triggers a warning and potential crash when setting file modification times, causing a denial of service.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: set ATTR_CTIME flags when setting mtime\n\nDavid reported that the new warning from setattr_copy_mgtime is coming\nlike the following.\n\n[  113.215316] ------------[ cut here ]------------\n[  113.215974] WARNING: CPU: 1 PID: 31 at fs/attr.c:300 setattr_copy+0x1ee/0x200\n[  113.219192] CPU: 1 UID: 0 PID: 31 Comm: kworker/1:1 Not tainted 6.13.0-rc1+ #234\n[  113.220127] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-rebuilt.opensuse.org 04/01/2014\n[  113.221530] Workqueue: ksmbd-io handle_ksmbd_work [ksmbd]\n[  113.222220] RIP: 0010:setattr_copy+0x1ee/0x200\n[  113.222833] Code: 24 28 49 8b 44 24 30 48 89 53 58 89 43 6c 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc 48 89 df e8 77 d6 ff ff e9 cd fe ff ff \u003c0f\u003e 0b e9 be fe ff ff 66 0\n[  113.225110] RSP: 0018:ffffaf218010fb68 EFLAGS: 00010202\n[  113.225765] RAX: 0000000000000120 RBX: ffffa446815f8568 RCX: 0000000000000003\n[  113.226667] RDX: ffffaf218010fd38 RSI: ffffa446815f8568 RDI: ffffffff94eb03a0\n[  113.227531] RBP: ffffaf218010fb90 R08: 0000001a251e217d R09: 00000000675259fa\n[  113.228426] R10: 0000000002ba8a6d R11: ffffa4468196c7a8 R12: ffffaf218010fd38\n[  113.229304] R13: 0000000000000120 R14: ffffffff94eb03a0 R15: 0000000000000000\n[  113.230210] FS:  0000000000000000(0000) GS:ffffa44739d00000(0000) knlGS:0000000000000000\n[  113.231215] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  113.232055] CR2: 00007efe0053d27e CR3: 000000000331a000 CR4: 00000000000006b0\n[  113.232926] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[  113.233812] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[  113.234797] Call Trace:\n[  113.235116]  \u003cTASK\u003e\n[  113.235393]  ? __warn+0x73/0xd0\n[  113.235802]  ? setattr_copy+0x1ee/0x200\n[  113.236299]  ? report_bug+0xf3/0x1e0\n[  113.236757]  ? handle_bug+0x4d/0x90\n[  113.237202]  ? exc_invalid_op+0x13/0x60\n[  113.237689]  ? asm_exc_invalid_op+0x16/0x20\n[  113.238185]  ? setattr_copy+0x1ee/0x200\n[  113.238692]  btrfs_setattr+0x80/0x820 [btrfs]\n[  113.239285]  ? get_stack_info_noinstr+0x12/0xf0\n[  113.239857]  ? __module_address+0x22/0xa0\n[  113.240368]  ? handle_ksmbd_work+0x6e/0x460 [ksmbd]\n[  113.240993]  ? __module_text_address+0x9/0x50\n[  113.241545]  ? __module_address+0x22/0xa0\n[  113.242033]  ? unwind_next_frame+0x10e/0x920\n[  113.242600]  ? __pfx_stack_trace_consume_entry+0x10/0x10\n[  113.243268]  notify_change+0x2c2/0x4e0\n[  113.243746]  ? stack_depot_save_flags+0x27/0x730\n[  113.244339]  ? set_file_basic_info+0x130/0x2b0 [ksmbd]\n[  113.244993]  set_file_basic_info+0x130/0x2b0 [ksmbd]\n[  113.245613]  ? process_scheduled_works+0xbe/0x310\n[  113.246181]  ? worker_thread+0x100/0x240\n[  113.246696]  ? kthread+0xc8/0x100\n[  113.247126]  ? ret_from_fork+0x2b/0x40\n[  113.247606]  ? ret_from_fork_asm+0x1a/0x30\n[  113.248132]  smb2_set_info+0x63f/0xa70 [ksmbd]\n\nksmbd is trying to set the atime and mtime via notify_change without also\nsetting the ctime. so This patch add ATTR_CTIME flags when setting mtime\nto avoid a warning.","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":"ksmbd: set ATTR_CTIME flags when setting mtime","id":"CVE-2024-57895","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"other","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"btrfs: flush delalloc workers queue before stopping cleaner kthread during unmount","id":"CVE-2024-57896"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2024-57894"},"products":["Linux"],"published":"2025-01-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 missing flag in the ksmbd kernel module triggers a warning and potential crash when setting file modification times, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2024-57895/"}