<?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-10-01T20:27:47.953474+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-2026-72297</id>
    <title>CVE-2026-72297 — net: atm: reject out-of-range traffic classes in QoS validation</title>
    <updated>2026-10-01T20:27:47.959280+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>net: atm: reject out-of-range traffic classes in QoS validation</p>
<p>Reject ATM traffic classes above ATM_ANYCLASS in check_tp().
SO_ATMQOS stores the supplied QoS after check_qos() succeeds, so
accepting larger values leaves invalid traffic_class values in
vcc-&gt;qos.</p>
<p>That bad state later reaches pvc_info(), which indexes class_name[]
with vcc-&gt;qos.{rx,tp}.traffic_class. Values above ATM_ANYCLASS cause
an out-of-bounds read when /proc/net/atm/pvc is read.</p>
<p>Tighten the existing QoS validation so invalid traffic_class values
are rejected at the point where user supplied QoS is accepted.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-72297"/>
  </entry>
</feed>
