CVE-2026-43065
MediumSummary
W jądrze Linuxa zidentyfikowano podatność w systemie plików ext4, która polega na tym, że po usunięciu plików i remountowaniu systemu z opcją nodiscard, oczekujące zadania związane z usuwaniem nie są anulowane ani opróżniane. Problem ten został rozwiązany w najnowszej aktualizacji.
Risk Assessment
Podatność ta może prowadzić do nieprzewidzianego zachowania systemu plików, co w przypadku ataku może skutkować utratą danych lub nieprawidłowym zarządzaniem przestrzenią dyskową.
Recommendation
Zaleca się aktualizację jądra Linux do najnowszej wersji, aby usunąć tę podatność i zapewnić prawidłowe działanie systemu plików ext4.
Related vulnerabilities
- CVE-2026-103041Critical
LightLLM through 1.2.0 multimodal deployments expose an unauthenticated RPyC cache service with pickle deserialization enabled on all interfaces. Attackers can send crafted serialized objects to exposed cache methods to execute arbitrary code with service privileges.
- CVE-2026-103040Critical
LightLLM through 1.2.0 contains a remote code execution vulnerability in the router profiler service when started with --enable_profiling flag. The service exposes an unauthenticated RPyC server with pickle deserialization enabled, allowing attackers to execute arbitrary code by sending crafted serialized objects to the profiler command queue.
- CVE-2026-102792Critical
A vulnerability was detected in Ziroom ZHOME A0101 1.0.1.0. This affects the function set_syslog of the file /api/ZRnetwork/set_syslog. The manipulation of the argument conloglevel/log_size results in command injection. The attack may be performed from remote. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
- CVE-2026-72510Critical
The "supplier_no" parameter used in the business allocation search feature is vulnerable to time-based blind SQL injection.
- CVE-2026-72507Critical
The "reportType" parameter in the product summary report feature within the balancing reports section is susceptible to a time-based blind SQL injection vulnerability.
- CVE-2026-71379Critical
The file export endpoint allows any unauthenticated attacker to export arbitrary database tables by sending a crafted POST request.
- CVE-2026-70356Critical
The TMS file upload endpoint fails to enforce server-side file type restrictions, allowing an attacker to upload and execute arbitrary PHP files on the web server.
- CVE-2026-68954Critical
The "pattern" parameter used in search function in the home page of the TMS application is vulnerable to time-based blind SQL injection vulnerability.
- CVE-2026-68068Critical
The "screenID" parameter in the electronic transaction queue viewer feature within the manual transactions section is susceptible to a time-based blind SQL injection vulnerability.
- CVE-2026-63713Critical
The "search" parameter in the view audit logs feature within the utilities section is susceptible to a time-based blind SQL injection vulnerability.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: ext4: always drain queued discard work in ext4_mb_release() While reviewing recent ext4 patch[1], Sashiko raised the following concern[2]: > If the filesystem is initially mounted with the discard option, > deleting files will populate sbi->s_discard_list and queue > s_discard_work. If it is then remounted with nodiscard, the > EXT4_MOUNT_DISCARD flag is cleared, but the pending s_discard_work is > neither cancelled nor flushed. [1] https://lore.kernel.org/r/[email protected]/ [2] https://sashiko.dev/#/patchset/20260319094545.19291-1-qiang.zhang%40linux.dev The concern was valid, but it had nothing to do with the patch[1]. One of the problems with Sashiko in its current (early) form is that it will detect pre-existing issues and report it as a problem with the patch that it is reviewing. In practice, it would be hard to hit deliberately (unless you are a malicious syzkaller fuzzer), since it would involve mounting the file system with -o discard, and then deleting a large number of files, remounting the file system with -o nodiscard, and then immediately unmounting the file system before the queued discard work has a change to drain on its own. Fix it because it's a real bug, and to avoid Sashiko from raising this concern when analyzing future patches to mballoc.c.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS