<?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/sightings/feed</id>
  <title>Most recent sightings.</title>
  <updated>2026-06-01T09:07:11.664884+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 sightings.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/sighting/b964e66e-830e-4e53-8e57-23b00535f4bf/export</id>
    <title>b964e66e-830e-4e53-8e57-23b00535f4bf</title>
    <updated>2026-06-01T09:07:12.131236+00:00</updated>
    <author>
      <name>Automation user</name>
      <uri>https://cve.circl.lu/user/automation</uri>
    </author>
    <content>{"uuid": "b964e66e-830e-4e53-8e57-23b00535f4bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-47646", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/5744", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2021-47646\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"Revert \"block, bfq: honor already-setup queue merges\"\"\n\nA crash [1] happened to be triggered in conjunction with commit\n2d52c58b9c9b (\"block, bfq: honor already-setup queue merges\"). The\nlatter was then reverted by commit ebc69e897e17 (\"Revert \"block, bfq:\nhonor already-setup queue merges\"\"). Yet, the reverted commit was not\nthe one introducing the bug. In fact, it actually triggered a UAF\nintroduced by a different commit, and now fixed by commit d29bd41428cf\n(\"block, bfq: reset last_bfqq_created on group change\").\n\nSo, there is no point in keeping commit 2d52c58b9c9b (\"block, bfq:\nhonor already-setup queue merges\") out. This commit restores it.\n\n[1] https://bugzilla.kernel.org/show_bug.cgi?id=214503\n\ud83d\udccf Published: 2025-02-26T01:54:15.122Z\n\ud83d\udccf Modified: 2025-02-27T18:02:30.637Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/f990f0985eda59d4f29fc83fcf300c92b1225d39\n2. https://git.kernel.org/stable/c/931aff627469a75c77b9fd3823146d0575afffd6\n3. https://git.kernel.org/stable/c/cc051f497eac9d8a0d816cd4bffa3415f2724871\n4. https://git.kernel.org/stable/c/65d8a737452e88f251fe5d925371de6d606df613\n5. https://git.kernel.org/stable/c/abc2129e646af7b43025d90a071f83043f1ae76c\n6. https://git.kernel.org/stable/c/4083925bd6dc89216d156474a8076feec904e607\n7. https://git.kernel.org/stable/c/15729ff8143f8135b03988a100a19e66d7cb7ecd", "creation_timestamp": "2025-02-27T18:27:04.000000Z"}</content>
    <link href="https://vulnerability.circl.lu/sighting/b964e66e-830e-4e53-8e57-23b00535f4bf/export"/>
    <published>2025-02-27T18:27:04+00:00</published>
  </entry>
</feed>
