<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T15:15:52.557922+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2023-53456</id>
    <title>CVE-2023-53456 — scsi: qla4xxx: Add length check when parsing nlattrs</title>
    <updated>2026-09-29T15:15:52.755347+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>scsi: qla4xxx: Add length check when parsing nlattrs</p>
<p>There are three places that qla4xxx parses nlattrs:</p>
<p>- qla4xxx_set_chap_entry()</p>
<p>- qla4xxx_iface_set_param()</p>
<p>- qla4xxx_sysfs_ddb_set_param()</p>
<p>and each of them directly converts the nlattr to specific pointer of
structure without length checking. This could be dangerous as those
attributes are not validated and a malformed nlattr (e.g., length 0) could
result in an OOB read that leaks heap dirty data.</p>
<p>Add the nla_len check before accessing the nlattr data and return EINVAL if
the length check fails.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-53456"/>
  </entry>
</feed>
