https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 23:49:17 +0000 https://vulnerability.circl.lu/vuln/cve-2026-80603 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read</p> <p>parse_dcc() treats data_end as an inclusive end pointer, but its only caller passes data_limit = ib_ptr + datalen, which points one past the last valid byte.</p> <p>The newline search loop iterates while tmp &lt;= data_end, so when no newline is present, *tmp is read at tmp == data_end, one byte beyond the region filled by skb_header_pointer().</p> <p>irc_buffer is kmalloc&#39;d as MAX_SEARCH_SIZE + 1 bytes and datalen is capped at MAX_SEARCH_SIZE, so the stray read does not fault. The byte is uninitialized or stale; if it contains an ASCII digit, simple_strtoul will consume it and produce a wrong DCC IP or port in the conntrack expectation. The extra allocation byte is also a fragile guard: if the cap or allocation size changes, this becomes a real out-of-bounds read.</p> <p>Change the loop and its post-loop check to use strict less-than, consistent with the caller&#39;s exclusive-end convention. Update the function comment accordingly.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read</p> <p>parse_dcc() treats data_end as an inclusive end pointer, but its only caller passes data_limit = ib_ptr + datalen, which points one past the last valid byte.</p> <p>The newline search loop iterates while tmp &lt;= data_end, so when no newline is present, *tmp is read at tmp == data_end, one byte beyond the region filled by skb_header_pointer().</p> <p>irc_buffer is kmalloc&#39;d as MAX_SEARCH_SIZE + 1 bytes and datalen is capped at MAX_SEARCH_SIZE, so the stray read does not fault. The byte is uninitialized or stale; if it contains an ASCII digit, simple_strtoul will consume it and produce a wrong DCC IP or port in the conntrack expectation. The extra allocation byte is also a fragile guard: if the cap or allocation size changes, this becomes a real out-of-bounds read.</p> <p>Change the loop and its post-loop check to use strict less-than, consistent with the caller&#39;s exclusive-end convention. Update the function comment accordingly.</p> https://vulnerability.circl.lu/vuln/cve-2026-80603