kernel: ext4: add bounds checking in get_max_inline_xattr_value_size()

In the Linux kernel, the following vulnerability has been resolved: ext4: add bounds checking in getmaxinlinexattrvaluesize Normally the extended attributes in the inode body would have been checked when the inode is first opened, but if someone is writing to the block device while the file syste...

SUSE CVE-2024-26927

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

CVE-2024-26927

A flaw was found in the Linux kernel. The following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data...

DEBIAN-CVE-2022-48632

In the Linux kernel, the following vulnerability has been resolved: i2c: mlxbf: prevent stack overflow in mlxbfi2csmbusstarttransaction memcpy is called in a loop while 'operation-length' upper bound is not checked and 'dataidx' also increments...

CVE-2024-26927

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

CVE-2024-26927

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

UBUNTU-CVE-2024-26927

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

CVE-2024-26927

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

CVE-2024-26927 ASoC: SOF: Add some bounds checking to firmware data

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

CVE-2024-26927 ASoC: SOF: Add some bounds checking to firmware data

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

CVE-2024-26927 ASoC: SOF: Add some bounds checking to firmware data

In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head-fullsize - head-headersize" can underflow. To some extent, we're always going to have to trust the firmware a bit. However, it's easy enough to add...

CVE-2024-25048 IBM MQ code execution

IBM MQ Appliance 9.3 CD and LTS are vulnerable to a heap-based buffer overflow, caused by improper bounds checking. A remote authenticated attacker could overflow a buffer and execute arbitrary code on the system or cause the server to crash. IBM X-Force ID: 283137...

Stack-Buffer Overflow

sngrep is vulnerable to a Stack-Buffer Overflow. The vulnerability is due to inadequate bounds checking when copying 'Content-Length' and 'Warning' headers into fixed-size buffers in the sipvalidatepacket and sipparseextraheaders functions within src/sip.c. It allows remote attackers to execute...

FFmpeg Buffer Overflow Vulnerability (CNVD-2024-27560)

FFmpeg is a complete solution for recording, converting and streaming audio and video from the FFmpeg team. A buffer overflow vulnerability exists in Ffmpeg version v.N113007-g8d24a28d06 due to incorrect bounds checking in the libavfilter/avfshowspectrum.c:1789:52 component of the...

FFmpeg Buffer Overflow Vulnerability (CNVD-2024-27561)

FFmpeg is a complete solution for recording, converting and streaming audio and video from the FFmpeg team. A buffer overflow vulnerability exists in Ffmpeg version v.N113007-g8d24a28d06 due to incorrect bounds checking of libavfilter/avfshowwaves.c:722:24 in the showwavesfilterframe, which can b...

FFmpeg buffer overflow vulnerability (CNVD-2024-27562)

FFmpeg is a complete solution for recording, converting and streaming audio and video from the FFmpeg team. A buffer overflow vulnerability exists in Ffmpeg version v.N113007-g8d24a28d06 due to incorrect bounds checking in libavfilter/freverse.c:269:26 in the areverserequestframe, which can be...

FFmpeg buffer overflow vulnerability (CNVD-2024-27563)

FFmpeg is a complete solution for recording, converting and streaming audio and video from the FFmpeg team. A buffer overflow vulnerability exists in Ffmpeg version v.N113007-g8d24a28d06 due to incorrect bounds checking as a result of a floating-point exception FPE error at...

Out-of-bounds Write

gtkwave is vulnerable to Out-of-bounds Write. The vulnerability is due to insufficient bounds checking in the in the VCD parsevaluechange portdump functionality via the GUI's legacy VCD parsing code, allows specially crafted .vcd file can lead to arbitrary code execution...

Out-of-bounds Write

gtkwave is vulnerable to Out-of-bounds Write. The vulnerability is due to inadequate bounds checking within its VCD parsevaluechange portdump functionality by the vcd2lxt2 conversion utility. It allows a Crafting a specially designed .vcd file can result in arbitrary code execution...

Out-of-bounds Write

gtkwave is vulnerable to Out-of-bounds Write. The vulnerability is due to insufficient bounds checking within its VCD parsevaluechange portdump functionality via the vcd2vzt conversion utility. It allows a Crafting a specially designed .vcd file can result in arbitrary code execution...