<?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://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T00:35:05.115718+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/bell-cve-2025-68774</id>
    <title>BELL-CVE-2025-68774</title>
    <updated>2026-11-21T00:35:05.125381+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2025-68774"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</id>
    <title>certfr-2026-avi-0166 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
    <updated>2026-11-21T00:35:05.125419+00:00</updated>
    <content>certfr-2026-avi-0166</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0166"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68774</id>
    <title>UBUNTU-CVE-2025-68774</title>
    <updated>2026-11-21T00:35:05.125434+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 232 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create When sync() and link() are called concurrently, both threads may enter hfs_bnode_find() without finding the node in the hash table and proceed to create it. Thread A:   hfsplus_write_inode()     -&gt; hfsplus_write_system_inode()       -&gt; hfs_btree_write()         -&gt; hfs_bnode_find(tree, 0)           -&gt; __hfs_bnode_create(tree, 0) Thread B:   hfsplus_create_cat()     -&gt; hfs_brec_insert()       -&gt; hfs_bnode_split()         -&gt; hfs_bmap_alloc()           -&gt; hfs_bnode_find(tree, 0)             -&gt; __hfs_bnode_create(tree, 0) In this case, thread A creates the bnode, sets refcnt=1, and hashes it. Thread B also tries to create the same bnode, notices it has already been inserted, drops its own instance, and uses the hashed one without getting the node. ``` 	node2 = hfs_bnode_findhash(tree, cnid); 	if (!node2) {                                 &lt;- Thread A 		hash = hfs_bnode_hash(cnid); 		node-&gt;next_hash = tree-&gt;node_hash[hash]; 		tree-&gt;node_hash[hash] = node; 		tree-&gt;node_hash_cnt++; 	} else {                                      &lt;- Thread B 		spin_unlock(&amp;tree-&gt;hash_lock); 		kfree(node); 		wait_event(node2-&gt;lock_wq, 			!test_bit(HFS_BNODE_NEW, &amp;node2-&gt;flags)); 		return node2; 	} ``` However, hfs_bnode_find() requires each call to take a reference. Here both threads end up setting refcnt=1. When they later put the node, this triggers: BUG_ON(!atomic_read(&amp;node-…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68774"/>
  </entry>
</feed>
