<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-02T07:16:20.786575+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/certfr-2026-avi-1375</id>
    <title>certfr-2026-avi-1375 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
    <updated>2026-11-02T07:16:20.836945+00:00</updated>
    <content>certfr-2026-avi-1375</content>
    <link href="https://db.gcve.eu/vuln/certfr-2026-avi-1375"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-98751</id>
    <title>fkie_cve-2026-98751</title>
    <updated>2026-11-02T07:16:20.837014+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tty: abort break signalling on hangup</p>
<p>The break ioctls can race with hangup and end up calling into a tty
driver for a device that is already gone or powered down.</p>
<p>Drivers must handle this race, but TCSBRK and TCSBRKP should still be
aborted to avoid calling back into the driver after a user-controlled
timeout (possibly even after the tty has been reopened).</p>
<p>Note that drivers should disable any break state on shutdown so just
return on hangup (calling break_ctl() again is racy and will most likely
fail for drivers handling the race).</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-98751"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-cg92-2wfv-ppg3</id>
    <title>GHSA-cg92-2wfv-ppg3</title>
    <updated>2026-11-02T07:16:20.837077+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tty: abort break signalling on hangup</p>
<p>The break ioctls can race with hangup and end up calling into a tty
driver for a device that is already gone or powered down.</p>
<p>Drivers must handle this race, but TCSBRK and TCSBRKP should still be
aborted to avoid calling back into the driver after a user-controlled
timeout (possibly even after the tty has been reopened).</p>
<p>Note that drivers should disable any break state on shutdown so just
return on hangup (calling break_ctl() again is racy and will most likely
fail for drivers handling the race).</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-cg92-2wfv-ppg3"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/msrc_cve-2026-98751</id>
    <title>msrc_CVE-2026-98751 — tty: abort break signalling on hangup</title>
    <updated>2026-11-02T07:16:20.837112+00:00</updated>
    <content>msrc_CVE-2026-98751</content>
    <link href="https://db.gcve.eu/vuln/msrc_cve-2026-98751"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ubuntu-cve-2026-98751</id>
    <title>UBUNTU-CVE-2026-98751</title>
    <updated>2026-11-02T07:16:20.837137+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 247 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: tty: abort break signalling on hangup The break ioctls can race with hangup and end up calling into a tty driver for a device that is already gone or powered down. Drivers must handle this race, but TCSBRK and TCSBRKP should still be aborted to avoid calling back into the driver after a user-controlled timeout (possibly even after the tty has been reopened). Note that drivers should disable any break state on shutdown so just return on hangup (calling break_ctl() again is racy and will most likely fail for drivers handling the race).</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ubuntu-cve-2026-98751"/>
  </entry>
</feed>
