<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 27 May 2026 14:02:01 +0000</lastBuildDate>
    <item>
      <title>6508674f-b579-4c30-b0d1-1b9478483bae</title>
      <link>https://vulnerability.circl.lu/sighting/6508674f-b579-4c30-b0d1-1b9478483bae/export</link>
      <description>{"uuid": "6508674f-b579-4c30-b0d1-1b9478483bae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50163", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113441350519511886", "content": "", "creation_timestamp": "2024-11-07T11:07:19.035484Z"}</description>
      <content:encoded>{"uuid": "6508674f-b579-4c30-b0d1-1b9478483bae", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50163", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113441350519511886", "content": "", "creation_timestamp": "2024-11-07T11:07:19.035484Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/6508674f-b579-4c30-b0d1-1b9478483bae/export</guid>
      <pubDate>Thu, 07 Nov 2024 11:07:19 +0000</pubDate>
    </item>
    <item>
      <title>6f3ea5c3-aef9-474e-88be-c296091f4491</title>
      <link>https://vulnerability.circl.lu/sighting/6f3ea5c3-aef9-474e-88be-c296091f4491/export</link>
      <description>{"uuid": "6f3ea5c3-aef9-474e-88be-c296091f4491", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50163", "type": "seen", "source": "https://t.me/cvedetector/10072", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50163 - Linux Kernel - BPF Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50163 \nPublished : Nov. 7, 2024, 10:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Make sure internal and UAPI bpf_redirect flags don't overlap  \n  \nThe bpf_redirect_info is shared between the SKB and XDP redirect paths,  \nand the two paths use the same numeric flag values in the ri-&amp;gt;flags  \nfield (specifically, BPF_F_BROADCAST == BPF_F_NEXTHOP). This means that  \nif skb bpf_redirect_neigh() is used with a non-NULL params argument and,  \nsubsequently, an XDP redirect is performed using the same  \nbpf_redirect_info struct, the XDP path will get confused and end up  \ncrashing, which syzbot managed to trigger.  \n  \nWith the stack-allocated bpf_redirect_info, the structure is no longer  \nshared between the SKB and XDP paths, so the crash doesn't happen  \nanymore. However, different code paths using identically-numbered flag  \nvalues in the same struct field still seems like a bit of a mess, so  \nthis patch cleans that up by moving the flag definitions together and  \nredefining the three flags in BPF_F_REDIRECT_INTERNAL to not overlap  \nwith the flags used for XDP. It also adds a BUILD_BUG_ON() check to make  \nsure the overlap is not re-introduced by mistake. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-07T11:54:30.000000Z"}</description>
      <content:encoded>{"uuid": "6f3ea5c3-aef9-474e-88be-c296091f4491", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50163", "type": "seen", "source": "https://t.me/cvedetector/10072", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50163 - Linux Kernel - BPF Bypass Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-50163 \nPublished : Nov. 7, 2024, 10:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Make sure internal and UAPI bpf_redirect flags don't overlap  \n  \nThe bpf_redirect_info is shared between the SKB and XDP redirect paths,  \nand the two paths use the same numeric flag values in the ri-&amp;gt;flags  \nfield (specifically, BPF_F_BROADCAST == BPF_F_NEXTHOP). This means that  \nif skb bpf_redirect_neigh() is used with a non-NULL params argument and,  \nsubsequently, an XDP redirect is performed using the same  \nbpf_redirect_info struct, the XDP path will get confused and end up  \ncrashing, which syzbot managed to trigger.  \n  \nWith the stack-allocated bpf_redirect_info, the structure is no longer  \nshared between the SKB and XDP paths, so the crash doesn't happen  \nanymore. However, different code paths using identically-numbered flag  \nvalues in the same struct field still seems like a bit of a mess, so  \nthis patch cleans that up by moving the flag definitions together and  \nredefining the three flags in BPF_F_REDIRECT_INTERNAL to not overlap  \nwith the flags used for XDP. It also adds a BUILD_BUG_ON() check to make  \nsure the overlap is not re-introduced by mistake. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-07T11:54:30.000000Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/6f3ea5c3-aef9-474e-88be-c296091f4491/export</guid>
      <pubDate>Thu, 07 Nov 2024 11:54:30 +0000</pubDate>
    </item>
  </channel>
</rss>
