<?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-29T05:04:04.708946+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-2024-46832</id>
    <title>CVE-2024-46832 — MIPS: cevt-r4k: Don't call get_c0_compare_int if timer irq is installed</title>
    <updated>2026-09-29T05:04:05.915613+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>MIPS: cevt-r4k: Don't call get_c0_compare_int if timer irq is installed</p>
<p>This avoids warning:</p>
<p>[    0.118053] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283</p>
<p>Caused by get_c0_compare_int on secondary CPU.</p>
<p>We also skipped saving IRQ number to struct clock_event_device *cd as
it's never used by clockevent core, as per comments it's only meant
for "non CPU local devices".</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-46832"/>
  </entry>
</feed>
