https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 03:15:08 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-06347 bdu:2024-06347 https://cve.radiocsirt.org/vuln/bdu:2024-06347 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0329 certfr-2024-avi-0329 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0329 https://cve.radiocsirt.org/vuln/euvd-2026-344337 EUVD-2026-344337 https://cve.radiocsirt.org/vuln/euvd-2026-344337 https://cve.radiocsirt.org/vuln/fkie_cve-2021-46933 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.</p> <p>ffs_data_clear is indirectly called from both ffs_fs_kill_sb and ffs_ep0_release, so it ends up being called twice when userland closes ep0 and then unmounts f_fs. If userland provided an eventfd along with function&#39;s USB descriptors, it ends up calling eventfd_ctx_put as many times, causing a refcount underflow. NULL-ify ffs_eventfd to prevent these extraneous eventfd_ctx_put calls.</p> <p>Also, set epfiles to NULL right after de-allocating it, for readability.</p> <p>For completeness, ffs_data_clear actually ends up being called thrice, the last call being before the whole ffs structure gets freed, so when this specific sequence happens there is a second underflow happening (but not being reported):</p> <p>/sys/kernel/debug/tracing# modprobe usb_f_fs /sys/kernel/debug/tracing# echo ffs_data_clear &gt; set_ftrace_filter /sys/kernel/debug/tracing# echo function &gt; current_tracer /sys/kernel/debug/tracing# echo 1 &gt; tracing_on (setup gadget, run and kill function userland process, teardown gadget) /sys/kernel/debug/tracing# echo 0 &gt; tracing_on /sys/kernel/debug/tracing# cat trace smartcard-openp-436 [000] ..... 1946.208786: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] ..... 1946.279147: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] .n... 1946.905512: ffs_data_clear &lt;-ffs_data_put</p> <p>Warning output corresponding to above trace: [ 194…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.</p> <p>ffs_data_clear is indirectly called from both ffs_fs_kill_sb and ffs_ep0_release, so it ends up being called twice when userland closes ep0 and then unmounts f_fs. If userland provided an eventfd along with function&#39;s USB descriptors, it ends up calling eventfd_ctx_put as many times, causing a refcount underflow. NULL-ify ffs_eventfd to prevent these extraneous eventfd_ctx_put calls.</p> <p>Also, set epfiles to NULL right after de-allocating it, for readability.</p> <p>For completeness, ffs_data_clear actually ends up being called thrice, the last call being before the whole ffs structure gets freed, so when this specific sequence happens there is a second underflow happening (but not being reported):</p> <p>/sys/kernel/debug/tracing# modprobe usb_f_fs /sys/kernel/debug/tracing# echo ffs_data_clear &gt; set_ftrace_filter /sys/kernel/debug/tracing# echo function &gt; current_tracer /sys/kernel/debug/tracing# echo 1 &gt; tracing_on (setup gadget, run and kill function userland process, teardown gadget) /sys/kernel/debug/tracing# echo 0 &gt; tracing_on /sys/kernel/debug/tracing# cat trace smartcard-openp-436 [000] ..... 1946.208786: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] ..... 1946.279147: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] .n... 1946.905512: ffs_data_clear &lt;-ffs_data_put</p> <p>Warning output corresponding to above trace: [ 194…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2021-46933 https://cve.radiocsirt.org/vuln/ghsa-w6v7-mjp2-pwcf <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.</p> <p>ffs_data_clear is indirectly called from both ffs_fs_kill_sb and ffs_ep0_release, so it ends up being called twice when userland closes ep0 and then unmounts f_fs. If userland provided an eventfd along with function&#39;s USB descriptors, it ends up calling eventfd_ctx_put as many times, causing a refcount underflow. NULL-ify ffs_eventfd to prevent these extraneous eventfd_ctx_put calls.</p> <p>Also, set epfiles to NULL right after de-allocating it, for readability.</p> <p>For completeness, ffs_data_clear actually ends up being called thrice, the last call being before the whole ffs structure gets freed, so when this specific sequence happens there is a second underflow happening (but not being reported):</p> <p>/sys/kernel/debug/tracing# modprobe usb_f_fs /sys/kernel/debug/tracing# echo ffs_data_clear &gt; set_ftrace_filter /sys/kernel/debug/tracing# echo function &gt; current_tracer /sys/kernel/debug/tracing# echo 1 &gt; tracing_on (setup gadget, run and kill function userland process, teardown gadget) /sys/kernel/debug/tracing# echo 0 &gt; tracing_on /sys/kernel/debug/tracing# cat trace smartcard-openp-436 [000] ..... 1946.208786: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] ..... 1946.279147: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] .n... 1946.905512: ffs_data_clear &lt;-ffs_data_put</p> <p>Warning output corresponding to above trace: [ 194…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear.</p> <p>ffs_data_clear is indirectly called from both ffs_fs_kill_sb and ffs_ep0_release, so it ends up being called twice when userland closes ep0 and then unmounts f_fs. If userland provided an eventfd along with function&#39;s USB descriptors, it ends up calling eventfd_ctx_put as many times, causing a refcount underflow. NULL-ify ffs_eventfd to prevent these extraneous eventfd_ctx_put calls.</p> <p>Also, set epfiles to NULL right after de-allocating it, for readability.</p> <p>For completeness, ffs_data_clear actually ends up being called thrice, the last call being before the whole ffs structure gets freed, so when this specific sequence happens there is a second underflow happening (but not being reported):</p> <p>/sys/kernel/debug/tracing# modprobe usb_f_fs /sys/kernel/debug/tracing# echo ffs_data_clear &gt; set_ftrace_filter /sys/kernel/debug/tracing# echo function &gt; current_tracer /sys/kernel/debug/tracing# echo 1 &gt; tracing_on (setup gadget, run and kill function userland process, teardown gadget) /sys/kernel/debug/tracing# echo 0 &gt; tracing_on /sys/kernel/debug/tracing# cat trace smartcard-openp-436 [000] ..... 1946.208786: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] ..... 1946.279147: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] .n... 1946.905512: ffs_data_clear &lt;-ffs_data_put</p> <p>Warning output corresponding to above trace: [ 194…</p> https://cve.radiocsirt.org/vuln/ghsa-w6v7-mjp2-pwcf https://cve.radiocsirt.org/vuln/gsd-2021-46933 gsd-2021-46933 https://cve.radiocsirt.org/vuln/gsd-2021-46933 https://cve.radiocsirt.org/vuln/suse-su-2024:1320-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:1320-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46933 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-kvm and 108 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear. ffs_data_clear is indirectly called from both ffs_fs_kill_sb and ffs_ep0_release, so it ends up being called twice when userland closes ep0 and then unmounts f_fs. If userland provided an eventfd along with function&#39;s USB descriptors, it ends up calling eventfd_ctx_put as many times, causing a refcount underflow. NULL-ify ffs_eventfd to prevent these extraneous eventfd_ctx_put calls. Also, set epfiles to NULL right after de-allocating it, for readability. For completeness, ffs_data_clear actually ends up being called thrice, the last call being before the whole ffs structure gets freed, so when this specific sequence happens there is a second underflow happening (but not being reported): /sys/kernel/debug/tracing# modprobe usb_f_fs /sys/kernel/debug/tracing# echo ffs_data_clear &gt; set_ftrace_filter /sys/kernel/debug/tracing# echo function &gt; current_tracer /sys/kernel/debug/tracing# echo 1 &gt; tracing_on (setup gadget, run and kill function userland process, teardown gadget) /sys/kernel/debug/tracing# echo 0 &gt; tracing_on /sys/kernel/debug/tracing# cat trace smartcard-openp-436 [000] ..... 1946.208786: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] ..... 1946.279147: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] .n... 1946.905512: ffs_data_clear &lt;-ffs_data_put Warning output corresponding to above trace: [ 1946.2841…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-kvm and 108 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Clear ffs_eventfd in ffs_data_clear. ffs_data_clear is indirectly called from both ffs_fs_kill_sb and ffs_ep0_release, so it ends up being called twice when userland closes ep0 and then unmounts f_fs. If userland provided an eventfd along with function&#39;s USB descriptors, it ends up calling eventfd_ctx_put as many times, causing a refcount underflow. NULL-ify ffs_eventfd to prevent these extraneous eventfd_ctx_put calls. Also, set epfiles to NULL right after de-allocating it, for readability. For completeness, ffs_data_clear actually ends up being called thrice, the last call being before the whole ffs structure gets freed, so when this specific sequence happens there is a second underflow happening (but not being reported): /sys/kernel/debug/tracing# modprobe usb_f_fs /sys/kernel/debug/tracing# echo ffs_data_clear &gt; set_ftrace_filter /sys/kernel/debug/tracing# echo function &gt; current_tracer /sys/kernel/debug/tracing# echo 1 &gt; tracing_on (setup gadget, run and kill function userland process, teardown gadget) /sys/kernel/debug/tracing# echo 0 &gt; tracing_on /sys/kernel/debug/tracing# cat trace smartcard-openp-436 [000] ..... 1946.208786: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] ..... 1946.279147: ffs_data_clear &lt;-ffs_data_closed smartcard-openp-431 [000] .n... 1946.905512: ffs_data_clear &lt;-ffs_data_put Warning output corresponding to above trace: [ 1946.2841…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-46933 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0488 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0488