The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade Echo:latest linux-6.12 to version 6.12.101-1~deb12u1 or higher.
Note: Versions mentioned in the description apply only to the upstream linux-6.12 package and not the linux-6.12 package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()
The ims_pcu_process_data() processes incoming URB data byte by byte.
However, it fails to check if the read_pos index exceeds
IMS_PCU_BUF_SIZE.
If a malicious USB device sends a packet larger than IMS_PCU_BUF_SIZE,
read_pos will increment indefinitely. Moreover, since read_pos is
located immediately after read_buf, the attacker can overwrite
read_pos itself to arbitrarily control the index.
This manipulated read_pos is subsequently used in
ims_pcu_handle_response() to copy data into cmd_buf, leading to a
heap buffer overflow.
Specifically, an attacker can overwrite the cmd_done.wait.head located
at offset 136 relative to cmd_buf in the ims_pcu_handle_response().
Consequently, when the driver calls complete(&pcu->cmd_done), it
triggers a control flow hijack by using the manipulated pointer.
Fix this by adding a bounds check for read_pos before writing to
read_buf. If the packet is too long, discard it, log a warning,
and reset the parser state.
[dtor: factor out resetting packet state, reset checksum as well]