https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 16:41:05 +0000 https://vulnerability.circl.lu/vuln/cve-2026-43380 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read</p> <p>The q54sj108a2_debugfs_read function suffers from a stack buffer overflow due to incorrect arguments passed to bin2hex(). The function currently passes &#39;data&#39; as the destination and &#39;data_char&#39; as the source.</p> <p>Because bin2hex() converts each input byte into two hex characters, a 32-byte block read results in 64 bytes of output. Since &#39;data&#39; is only 34 bytes (I2C_SMBUS_BLOCK_MAX + 2), this writes 30 bytes past the end of the buffer onto the stack.</p> <p>Additionally, the arguments were swapped: it was reading from the zero-initialized &#39;data_char&#39; and writing to &#39;data&#39;, resulting in all-zero output regardless of the actual I2C read.</p> <p>Fix this by: 1. Expanding &#39;data_char&#39; to 66 bytes to safely hold the hex output. 2. Correcting the bin2hex() argument order and using the actual read count. 3. Using a pointer to select the correct output buffer for the final simple_read_from_buffer call.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read</p> <p>The q54sj108a2_debugfs_read function suffers from a stack buffer overflow due to incorrect arguments passed to bin2hex(). The function currently passes &#39;data&#39; as the destination and &#39;data_char&#39; as the source.</p> <p>Because bin2hex() converts each input byte into two hex characters, a 32-byte block read results in 64 bytes of output. Since &#39;data&#39; is only 34 bytes (I2C_SMBUS_BLOCK_MAX + 2), this writes 30 bytes past the end of the buffer onto the stack.</p> <p>Additionally, the arguments were swapped: it was reading from the zero-initialized &#39;data_char&#39; and writing to &#39;data&#39;, resulting in all-zero output regardless of the actual I2C read.</p> <p>Fix this by: 1. Expanding &#39;data_char&#39; to 66 bytes to safely hold the hex output. 2. Correcting the bin2hex() argument order and using the actual read count. 3. Using a pointer to select the correct output buffer for the final simple_read_from_buffer call.</p> https://vulnerability.circl.lu/vuln/cve-2026-43380