GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2022-49093 (GCVE-0-2022-49093)

Vulnerability from cvelistv5 – Published: 2025-02-26 01:54 – Updated: 2026-08-05 08:53
VLAI
Title
skbuff: fix coalescing for page_pool fragment recycling
Summary
In the Linux kernel, the following vulnerability has been resolved: skbuff: fix coalescing for page_pool fragment recycling Fix a use-after-free when using page_pool with page fragments. We encountered this problem during normal RX in the hns3 driver: (1) Initially we have three descriptors in the RX queue. The first one allocates PAGE1 through page_pool, and the other two allocate one half of PAGE2 each. Page references look like this: RX_BD1 _______ PAGE1 RX_BD2 _______ PAGE2 RX_BD3 _________/ (2) Handle RX on the first descriptor. Allocate SKB1, eventually added to the receive queue by tcp_queue_rcv(). (3) Handle RX on the second descriptor. Allocate SKB2 and pass it to netif_receive_skb(): netif_receive_skb(SKB2) ip_rcv(SKB2) SKB3 = skb_clone(SKB2) SKB2 and SKB3 share a reference to PAGE2 through skb_shinfo()->dataref. The other ref to PAGE2 is still held by RX_BD3: SKB2 ---+- PAGE2 SKB3 __/ / RX_BD3 _________/ (3b) Now while handling TCP, coalesce SKB3 with SKB1: tcp_v4_rcv(SKB3) tcp_try_coalesce(to=SKB1, from=SKB3) // succeeds kfree_skb_partial(SKB3) skb_release_data(SKB3) // drops one dataref SKB1 _____ PAGE1 \____ SKB2 _____ PAGE2 / RX_BD3 _________/ In skb_try_coalesce(), __skb_frag_ref() takes a page reference to PAGE2, where it should instead have increased the page_pool frag reference, pp_frag_count. Without coalescing, when releasing both SKB2 and SKB3, a single reference to PAGE2 would be dropped. Now when releasing SKB1 and SKB2, two references to PAGE2 will be dropped, resulting in underflow. (3c) Drop SKB2: af_packet_rcv(SKB2) consume_skb(SKB2) skb_release_data(SKB2) // drops second dataref page_pool_return_skb_page(PAGE2) // drops one pp_frag_count SKB1 _____ PAGE1 \____ PAGE2 / RX_BD3 _________/ (4) Userspace calls recvmsg() Copies SKB1 and releases it. Since SKB3 was coalesced with SKB1, we release the SKB3 page as well: tcp_eat_recv_skb(SKB1) skb_release_data(SKB1) page_pool_return_skb_page(PAGE1) page_pool_return_skb_page(PAGE2) // drops second pp_frag_count (5) PAGE2 is freed, but the third RX descriptor was still using it! In our case this causes IOMMU faults, but it would silently corrupt memory if the IOMMU was disabled. Change the logic that checks whether pp_recycle SKBs can be coalesced. We still reject differing pp_recycle between 'from' and 'to' SKBs, but in order to avoid the situation described above, we also reject coalescing when both 'from' and 'to' are pp_recycled and 'from' is cloned. The new logic allows coalescing a cloned pp_recycle SKB into a page refcounted one, because in this case the release (4) will drop the right reference, the one taken by skb_try_coalesce().
Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SSVC
Exploitation: none Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-02-27 18:17 UTC
CWE
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 53e0961da1c7bbdabd1abebb20de403ec237ec09 , < ba965e8605aee5387cecaa28fcf7ee9f61779a49 (git)
Affected: 53e0961da1c7bbdabd1abebb20de403ec237ec09 , < c4fa19615806a9a7e518c295b39175aa47a685ac (git)
Affected: 53e0961da1c7bbdabd1abebb20de403ec237ec09 , < 72bb856d16e883437023ff2ff77d0c498018728a (git)
Affected: 53e0961da1c7bbdabd1abebb20de403ec237ec09 , < 1effe8ca4e34c34cdd9318436a4232dcb582ebf4 (git)
guessed Create a notification for this product.
Linux Linux Affected: 5.15
Unaffected: 0 , < 5.15 (semver)
Unaffected: 5.15.34 , ≤ 5.15.* (semver)
Unaffected: 5.16.20 , ≤ 5.16.* (semver)
Unaffected: 5.17.3 , ≤ 5.17.* (semver)
Unaffected: 5.18 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 7.8,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "HIGH",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2022-49093",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-02-27T18:17:26.547109Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-416",
                "description": "CWE-416 Use After Free",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-02-27T18:22:35.237Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/core/skbuff.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "ba965e8605aee5387cecaa28fcf7ee9f61779a49",
              "status": "affected",
              "version": "53e0961da1c7bbdabd1abebb20de403ec237ec09",
              "versionType": "git"
            },
            {
              "lessThan": "c4fa19615806a9a7e518c295b39175aa47a685ac",
              "status": "affected",
              "version": "53e0961da1c7bbdabd1abebb20de403ec237ec09",
              "versionType": "git"
            },
            {
              "lessThan": "72bb856d16e883437023ff2ff77d0c498018728a",
              "status": "affected",
              "version": "53e0961da1c7bbdabd1abebb20de403ec237ec09",
              "versionType": "git"
            },
            {
              "lessThan": "1effe8ca4e34c34cdd9318436a4232dcb582ebf4",
              "status": "affected",
              "version": "53e0961da1c7bbdabd1abebb20de403ec237ec09",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/core/skbuff.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.15"
            },
            {
              "lessThan": "5.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.34",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.16.*",
              "status": "unaffected",
              "version": "5.16.20",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.17.*",
              "status": "unaffected",
              "version": "5.17.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "5.18",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.34",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.16.20",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.17.3",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.18",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nskbuff: fix coalescing for page_pool fragment recycling\n\nFix a use-after-free when using page_pool with page fragments. We\nencountered this problem during normal RX in the hns3 driver:\n\n(1) Initially we have three descriptors in the RX queue. The first one\n    allocates PAGE1 through page_pool, and the other two allocate one\n    half of PAGE2 each. Page references look like this:\n\n                RX_BD1 _______ PAGE1\n                RX_BD2 _______ PAGE2\n                RX_BD3 _________/\n\n(2) Handle RX on the first descriptor. Allocate SKB1, eventually added\n    to the receive queue by tcp_queue_rcv().\n\n(3) Handle RX on the second descriptor. Allocate SKB2 and pass it to\n    netif_receive_skb():\n\n    netif_receive_skb(SKB2)\n      ip_rcv(SKB2)\n        SKB3 = skb_clone(SKB2)\n\n    SKB2 and SKB3 share a reference to PAGE2 through\n    skb_shinfo()-\u003edataref. The other ref to PAGE2 is still held by\n    RX_BD3:\n\n                      SKB2 ---+- PAGE2\n                      SKB3 __/   /\n                RX_BD3 _________/\n\n (3b) Now while handling TCP, coalesce SKB3 with SKB1:\n\n      tcp_v4_rcv(SKB3)\n        tcp_try_coalesce(to=SKB1, from=SKB3)    // succeeds\n        kfree_skb_partial(SKB3)\n          skb_release_data(SKB3)                // drops one dataref\n\n                      SKB1 _____ PAGE1\n                           \\____\n                      SKB2 _____ PAGE2\n                                 /\n                RX_BD3 _________/\n\n    In skb_try_coalesce(), __skb_frag_ref() takes a page reference to\n    PAGE2, where it should instead have increased the page_pool frag\n    reference, pp_frag_count. Without coalescing, when releasing both\n    SKB2 and SKB3, a single reference to PAGE2 would be dropped. Now\n    when releasing SKB1 and SKB2, two references to PAGE2 will be\n    dropped, resulting in underflow.\n\n (3c) Drop SKB2:\n\n      af_packet_rcv(SKB2)\n        consume_skb(SKB2)\n          skb_release_data(SKB2)                // drops second dataref\n            page_pool_return_skb_page(PAGE2)    // drops one pp_frag_count\n\n                      SKB1 _____ PAGE1\n                           \\____\n                                 PAGE2\n                                 /\n                RX_BD3 _________/\n\n(4) Userspace calls recvmsg()\n    Copies SKB1 and releases it. Since SKB3 was coalesced with SKB1, we\n    release the SKB3 page as well:\n\n    tcp_eat_recv_skb(SKB1)\n      skb_release_data(SKB1)\n        page_pool_return_skb_page(PAGE1)\n        page_pool_return_skb_page(PAGE2)        // drops second pp_frag_count\n\n(5) PAGE2 is freed, but the third RX descriptor was still using it!\n    In our case this causes IOMMU faults, but it would silently corrupt\n    memory if the IOMMU was disabled.\n\nChange the logic that checks whether pp_recycle SKBs can be coalesced.\nWe still reject differing pp_recycle between \u0027from\u0027 and \u0027to\u0027 SKBs, but\nin order to avoid the situation described above, we also reject\ncoalescing when both \u0027from\u0027 and \u0027to\u0027 are pp_recycled and \u0027from\u0027 is\ncloned.\n\nThe new logic allows coalescing a cloned pp_recycle SKB into a page\nrefcounted one, because in this case the release (4) will drop the right\nreference, the one taken by skb_try_coalesce()."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 9.8,
            "baseSeverity": "CRITICAL",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The bug is in skb_try_coalesce() on the TCP receive path (tcp_try_coalesce \u2190 tcp_queue_rcv / backlog), reached when a page_pool-frag NIC (hns3, mlx5, etc.) delivers attacker-sent TCP segments; remote peer traffic drives the vulnerable coalesce after normal RX, with no local syscall required.\nAC:L - The attacker controls TCP segment sequencing that triggers coalescing, and the remaining conditions (PP_FLAG_PAGE_FRAG NIC plus an skb clone from AF_PACKET/monitoring taps) are ordinary production deployments rather than races or memory-layout preconditions outside attacker influence.\nPR:N - No host credentials or capabilities are required\u2014an unauthenticated remote peer that opens or uses a TCP session to a network-facing service exercises the RX/coalesce path with no authentication gate on skbuff processing.\nUI:N - Exploitation needs only attacker-generated TCP traffic consumed by an already-running service (recvmsg on the coalesced skb); no separate victim action such as mounting a filesystem or opening a file is required.\nS:U - The pp_frag_count underflow frees a page still held by an RX descriptor within the host kernel networking authority; this is same-host memory corruption, not a VM escape or intentional IOMMU/security-boundary bypass.\nC:H - This is a use-after-free of a page_pool fragment page that remains DMA-mapped for RX, so the page can be reallocated to other kernel objects while still readable via residual skb/DMA paths\u2014leverageable for arbitrary kernel memory disclosure.\nI:H - The same UAF lets the NIC DMA into a page reused by other kernel allocations (or allows reclaim/spray of the freed page), yielding memory corruption and control-flow hijacking primitives consistent with High integrity impact for UAFs.\nA:H - The commit reports IOMMU faults when the still-mapped RX descriptor page is freed, and without IOMMU silent corruption that can oops/panic; UAFs of this form are Availability High under kernel CVSS guidance."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T08:53:53.011Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/ba965e8605aee5387cecaa28fcf7ee9f61779a49"
        },
        {
          "url": "https://git.kernel.org/stable/c/c4fa19615806a9a7e518c295b39175aa47a685ac"
        },
        {
          "url": "https://git.kernel.org/stable/c/72bb856d16e883437023ff2ff77d0c498018728a"
        },
        {
          "url": "https://git.kernel.org/stable/c/1effe8ca4e34c34cdd9318436a4232dcb582ebf4"
        }
      ],
      "title": "skbuff: fix coalescing for page_pool fragment recycling",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-49093",
    "datePublished": "2025-02-26T01:54:47.669Z",
    "dateReserved": "2025-02-26T01:49:39.249Z",
    "dateUpdated": "2026-08-05T08:53:53.011Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2022-49093",
      "date": "2026-09-14",
      "epss": "0.00617",
      "percentile": "0.47667"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2022-49093\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-02-26T07:00:46.633\",\"lastModified\":\"2026-08-04T10:17:34.567\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nskbuff: fix coalescing for page_pool fragment recycling\\n\\nFix a use-after-free when using page_pool with page fragments. We\\nencountered this problem during normal RX in the hns3 driver:\\n\\n(1) Initially we have three descriptors in the RX queue. The first one\\n    allocates PAGE1 through page_pool, and the other two allocate one\\n    half of PAGE2 each. Page references look like this:\\n\\n                RX_BD1 _______ PAGE1\\n                RX_BD2 _______ PAGE2\\n                RX_BD3 _________/\\n\\n(2) Handle RX on the first descriptor. Allocate SKB1, eventually added\\n    to the receive queue by tcp_queue_rcv().\\n\\n(3) Handle RX on the second descriptor. Allocate SKB2 and pass it to\\n    netif_receive_skb():\\n\\n    netif_receive_skb(SKB2)\\n      ip_rcv(SKB2)\\n        SKB3 = skb_clone(SKB2)\\n\\n    SKB2 and SKB3 share a reference to PAGE2 through\\n    skb_shinfo()-\u003edataref. The other ref to PAGE2 is still held by\\n    RX_BD3:\\n\\n                      SKB2 ---+- PAGE2\\n                      SKB3 __/   /\\n                RX_BD3 _________/\\n\\n (3b) Now while handling TCP, coalesce SKB3 with SKB1:\\n\\n      tcp_v4_rcv(SKB3)\\n        tcp_try_coalesce(to=SKB1, from=SKB3)    // succeeds\\n        kfree_skb_partial(SKB3)\\n          skb_release_data(SKB3)                // drops one dataref\\n\\n                      SKB1 _____ PAGE1\\n                           \\\\____\\n                      SKB2 _____ PAGE2\\n                                 /\\n                RX_BD3 _________/\\n\\n    In skb_try_coalesce(), __skb_frag_ref() takes a page reference to\\n    PAGE2, where it should instead have increased the page_pool frag\\n    reference, pp_frag_count. Without coalescing, when releasing both\\n    SKB2 and SKB3, a single reference to PAGE2 would be dropped. Now\\n    when releasing SKB1 and SKB2, two references to PAGE2 will be\\n    dropped, resulting in underflow.\\n\\n (3c) Drop SKB2:\\n\\n      af_packet_rcv(SKB2)\\n        consume_skb(SKB2)\\n          skb_release_data(SKB2)                // drops second dataref\\n            page_pool_return_skb_page(PAGE2)    // drops one pp_frag_count\\n\\n                      SKB1 _____ PAGE1\\n                           \\\\____\\n                                 PAGE2\\n                                 /\\n                RX_BD3 _________/\\n\\n(4) Userspace calls recvmsg()\\n    Copies SKB1 and releases it. Since SKB3 was coalesced with SKB1, we\\n    release the SKB3 page as well:\\n\\n    tcp_eat_recv_skb(SKB1)\\n      skb_release_data(SKB1)\\n        page_pool_return_skb_page(PAGE1)\\n        page_pool_return_skb_page(PAGE2)        // drops second pp_frag_count\\n\\n(5) PAGE2 is freed, but the third RX descriptor was still using it!\\n    In our case this causes IOMMU faults, but it would silently corrupt\\n    memory if the IOMMU was disabled.\\n\\nChange the logic that checks whether pp_recycle SKBs can be coalesced.\\nWe still reject differing pp_recycle between \u0027from\u0027 and \u0027to\u0027 SKBs, but\\nin order to avoid the situation described above, we also reject\\ncoalescing when both \u0027from\u0027 and \u0027to\u0027 are pp_recycled and \u0027from\u0027 is\\ncloned.\\n\\nThe new logic allows coalescing a cloned pp_recycle SKB into a page\\nrefcounted one, because in this case the release (4) will drop the right\\nreference, the one taken by skb_try_coalesce().\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: skbuff: correcci\u00f3n de coalescencia para reciclaje de fragmentos de page_pool Corrige un use-after-free al usar page_pool con fragmentos de p\u00e1gina. Encontramos este problema durante RX normal en el controlador hns3: (1) Inicialmente tenemos tres descriptores en la cola RX. El primero asigna PAGE1 a trav\u00e9s de page_pool, y los otros dos asignan la mitad de PAGE2 cada uno. Las referencias de p\u00e1gina se ven as\u00ed: RX_BD1 _______ PAGE1 RX_BD2 _______ PAGE2 RX_BD3 _________/ (2) Manejar RX en el primer descriptor. Asignar SKB1, eventualmente agregado a la cola de recepci\u00f3n por tcp_queue_rcv(). (3) Manejar RX en el segundo descriptor. Asigne SKB2 y p\u00e1selo a netif_receive_skb(): netif_receive_skb(SKB2) ip_rcv(SKB2) SKB3 = skb_clone(SKB2) SKB2 y SKB3 comparten una referencia a PAGE2 a trav\u00e9s de skb_shinfo()-\u0026gt;dataref. La otra referencia a PAGE2 todav\u00eda la mantiene RX_BD3: SKB2 ---+- PAGE2 SKB3 __/ / RX_BD3 _________/ (3b) Ahora, mientras maneja TCP, fusione SKB3 con SKB1: tcp_v4_rcv(SKB3) tcp_try_coalesce(to=SKB1, from=SKB3) // tiene \u00e9xito kfree_skb_partial(SKB3) skb_release_data(SKB3) // elimina una referencia de datos SKB1 _____ PAGE1 \\\\____ SKB2 _____ PAGE2 / RX_BD3 _________/ En skb_try_coalesce(), __skb_frag_ref() toma una referencia de p\u00e1gina a PAGE2, donde en cambio deber\u00eda haber aumentado la referencia de fragmento de page_pool, pp_frag_count. Sin la fusi\u00f3n, al liberar SKB2 y SKB3, se eliminar\u00eda una \u00fanica referencia a PAGE2. Ahora, al liberar SKB1 y SKB2, se descartar\u00e1n dos referencias a PAGE2, lo que provocar\u00e1 un desbordamiento. (3c) Descartar SKB2: af_packet_rcv(SKB2) consume_skb(SKB2) skb_release_data(SKB2) // descarta la segunda referencia de datos page_pool_return_skb_page(PAGE2) // descarta una pp_frag_count SKB1 _____ PAGE1 \\\\____ PAGE2 / RX_BD3 _________/ (4) El espacio de usuario llama a recvmsg() Copia SKB1 y lo libera. Dado que SKB3 se fusion\u00f3 con SKB1, tambi\u00e9n liberamos la p\u00e1gina SKB3: tcp_eat_recv_skb(SKB1) skb_release_data(SKB1) page_pool_return_skb_page(PAGE1) page_pool_return_skb_page(PAGE2) // elimina el segundo pp_frag_count (5) PAGE2 se libera, \u00a1pero el tercer descriptor RX todav\u00eda lo estaba usando! En nuestro caso, esto causa fallas de IOMMU, pero corromper\u00eda silenciosamente la memoria si IOMMU estuviera deshabilitado. Cambie la l\u00f3gica que verifica si los SKB pp_recycle se pueden fusionar. A\u00fan rechazamos diferentes pp_recycle entre SKB \u0027from\u0027 y \u0027to\u0027, pero para evitar la situaci\u00f3n descrita anteriormente, tambi\u00e9n rechazamos la fusi\u00f3n cuando tanto \u0027from\u0027 como \u0027to\u0027 son pp_recycled y \u0027from\u0027 es clonado. La nueva l\u00f3gica permite fusionar un SKB pp_recycle clonado en uno con referencia de p\u00e1gina, porque en este caso la versi\u00f3n (4) eliminar\u00e1 la referencia correcta, la tomada por skb_try_coalesce().\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"net/core/skbuff.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"53e0961da1c7bbdabd1abebb20de403ec237ec09\",\"lessThan\":\"ba965e8605aee5387cecaa28fcf7ee9f61779a49\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"53e0961da1c7bbdabd1abebb20de403ec237ec09\",\"lessThan\":\"c4fa19615806a9a7e518c295b39175aa47a685ac\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"53e0961da1c7bbdabd1abebb20de403ec237ec09\",\"lessThan\":\"72bb856d16e883437023ff2ff77d0c498018728a\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"53e0961da1c7bbdabd1abebb20de403ec237ec09\",\"lessThan\":\"1effe8ca4e34c34cdd9318436a4232dcb582ebf4\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"net/core/skbuff.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.15\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.15\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.34\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.16.20\",\"lessThanOrEqual\":\"5.16.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.17.3\",\"lessThanOrEqual\":\"5.17.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.18\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":9.8,\"baseSeverity\":\"CRITICAL\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":5.9},{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2025-02-27T18:17:26.547109Z\",\"id\":\"CVE-2022-49093\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"total\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-416\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.15\",\"versionEndExcluding\":\"5.15.34\",\"matchCriteriaId\":\"918697A2-B45C-4A04-8049-AFAB4BE2444E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"5.16.20\",\"matchCriteriaId\":\"ABBBA66E-0244-4621-966B-9790AF1EEB00\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.17\",\"versionEndExcluding\":\"5.17.3\",\"matchCriteriaId\":\"AE420AC7-1E59-4398-B84F-71F4B4337762\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.18:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"6AD94161-84BB-42E6-9882-4FC0C42E9FC1\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1effe8ca4e34c34cdd9318436a4232dcb582ebf4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/72bb856d16e883437023ff2ff77d0c498018728a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ba965e8605aee5387cecaa28fcf7ee9f61779a49\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c4fa19615806a9a7e518c295b39175aa47a685ac\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-06-29T20:57:45+00:00",
      "cve": "CVE-2022-49093",
      "id": "CVE-2022-49093",
      "initial_release_date": "2022-01-01T00:00:00+00:00",
      "product_status:fixed": "166",
      "product_status:known_affected": "14",
      "product_status:known_not_affected": "174",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: skbuff: fix coalescing for page_pool fragment recycling",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-49093.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-29T02:30:28Z",
      "cve": "CVE-2022-49093",
      "id": "CVE-2022-49093",
      "initial_release_date": "2025-02-27T03:12:23Z",
      "product_status:known_affected": "334",
      "product_status:known_not_affected": "401",
      "product_status:recommended": "245",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2022-49093",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2022-49093.json",
      "version": "41"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 7.8, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\", \"integrityImpact\": \"HIGH\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-49093\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-02-27T18:17:26.547109Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-416\", \"description\": \"CWE-416 Use After Free\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-02-27T18:17:27.887Z\"}}], \"cna\": {\"title\": \"skbuff: fix coalescing for page_pool fragment recycling\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 9.8, \"baseSeverity\": \"CRITICAL\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:N - The bug is in skb_try_coalesce() on the TCP receive path (tcp_try_coalesce \\u2190 tcp_queue_rcv / backlog), reached when a page_pool-frag NIC (hns3, mlx5, etc.) delivers attacker-sent TCP segments; remote peer traffic drives the vulnerable coalesce after normal RX, with no local syscall required.\\nAC:L - The attacker controls TCP segment sequencing that triggers coalescing, and the remaining conditions (PP_FLAG_PAGE_FRAG NIC plus an skb clone from AF_PACKET/monitoring taps) are ordinary production deployments rather than races or memory-layout preconditions outside attacker influence.\\nPR:N - No host credentials or capabilities are required\\u2014an unauthenticated remote peer that opens or uses a TCP session to a network-facing service exercises the RX/coalesce path with no authentication gate on skbuff processing.\\nUI:N - Exploitation needs only attacker-generated TCP traffic consumed by an already-running service (recvmsg on the coalesced skb); no separate victim action such as mounting a filesystem or opening a file is required.\\nS:U - The pp_frag_count underflow frees a page still held by an RX descriptor within the host kernel networking authority; this is same-host memory corruption, not a VM escape or intentional IOMMU/security-boundary bypass.\\nC:H - This is a use-after-free of a page_pool fragment page that remains DMA-mapped for RX, so the page can be reallocated to other kernel objects while still readable via residual skb/DMA paths\\u2014leverageable for arbitrary kernel memory disclosure.\\nI:H - The same UAF lets the NIC DMA into a page reused by other kernel allocations (or allows reclaim/spray of the freed page), yielding memory corruption and control-flow hijacking primitives consistent with High integrity impact for UAFs.\\nA:H - The commit reports IOMMU faults when the still-mapped RX descriptor page is freed, and without IOMMU silent corruption that can oops/panic; UAFs of this form are Availability High under kernel CVSS guidance.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"53e0961da1c7bbdabd1abebb20de403ec237ec09\", \"lessThan\": \"ba965e8605aee5387cecaa28fcf7ee9f61779a49\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"53e0961da1c7bbdabd1abebb20de403ec237ec09\", \"lessThan\": \"c4fa19615806a9a7e518c295b39175aa47a685ac\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"53e0961da1c7bbdabd1abebb20de403ec237ec09\", \"lessThan\": \"72bb856d16e883437023ff2ff77d0c498018728a\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"53e0961da1c7bbdabd1abebb20de403ec237ec09\", \"lessThan\": \"1effe8ca4e34c34cdd9318436a4232dcb582ebf4\", \"versionType\": \"git\"}], \"programFiles\": [\"net/core/skbuff.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.15\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.15\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.34\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"5.16.20\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.16.*\"}, {\"status\": \"unaffected\", \"version\": \"5.17.3\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.17.*\"}, {\"status\": \"unaffected\", \"version\": \"5.18\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"net/core/skbuff.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/ba965e8605aee5387cecaa28fcf7ee9f61779a49\"}, {\"url\": \"https://git.kernel.org/stable/c/c4fa19615806a9a7e518c295b39175aa47a685ac\"}, {\"url\": \"https://git.kernel.org/stable/c/72bb856d16e883437023ff2ff77d0c498018728a\"}, {\"url\": \"https://git.kernel.org/stable/c/1effe8ca4e34c34cdd9318436a4232dcb582ebf4\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nskbuff: fix coalescing for page_pool fragment recycling\\n\\nFix a use-after-free when using page_pool with page fragments. We\\nencountered this problem during normal RX in the hns3 driver:\\n\\n(1) Initially we have three descriptors in the RX queue. The first one\\n    allocates PAGE1 through page_pool, and the other two allocate one\\n    half of PAGE2 each. Page references look like this:\\n\\n                RX_BD1 _______ PAGE1\\n                RX_BD2 _______ PAGE2\\n                RX_BD3 _________/\\n\\n(2) Handle RX on the first descriptor. Allocate SKB1, eventually added\\n    to the receive queue by tcp_queue_rcv().\\n\\n(3) Handle RX on the second descriptor. Allocate SKB2 and pass it to\\n    netif_receive_skb():\\n\\n    netif_receive_skb(SKB2)\\n      ip_rcv(SKB2)\\n        SKB3 = skb_clone(SKB2)\\n\\n    SKB2 and SKB3 share a reference to PAGE2 through\\n    skb_shinfo()-\u003edataref. The other ref to PAGE2 is still held by\\n    RX_BD3:\\n\\n                      SKB2 ---+- PAGE2\\n                      SKB3 __/   /\\n                RX_BD3 _________/\\n\\n (3b) Now while handling TCP, coalesce SKB3 with SKB1:\\n\\n      tcp_v4_rcv(SKB3)\\n        tcp_try_coalesce(to=SKB1, from=SKB3)    // succeeds\\n        kfree_skb_partial(SKB3)\\n          skb_release_data(SKB3)                // drops one dataref\\n\\n                      SKB1 _____ PAGE1\\n                           \\\\____\\n                      SKB2 _____ PAGE2\\n                                 /\\n                RX_BD3 _________/\\n\\n    In skb_try_coalesce(), __skb_frag_ref() takes a page reference to\\n    PAGE2, where it should instead have increased the page_pool frag\\n    reference, pp_frag_count. Without coalescing, when releasing both\\n    SKB2 and SKB3, a single reference to PAGE2 would be dropped. Now\\n    when releasing SKB1 and SKB2, two references to PAGE2 will be\\n    dropped, resulting in underflow.\\n\\n (3c) Drop SKB2:\\n\\n      af_packet_rcv(SKB2)\\n        consume_skb(SKB2)\\n          skb_release_data(SKB2)                // drops second dataref\\n            page_pool_return_skb_page(PAGE2)    // drops one pp_frag_count\\n\\n                      SKB1 _____ PAGE1\\n                           \\\\____\\n                                 PAGE2\\n                                 /\\n                RX_BD3 _________/\\n\\n(4) Userspace calls recvmsg()\\n    Copies SKB1 and releases it. Since SKB3 was coalesced with SKB1, we\\n    release the SKB3 page as well:\\n\\n    tcp_eat_recv_skb(SKB1)\\n      skb_release_data(SKB1)\\n        page_pool_return_skb_page(PAGE1)\\n        page_pool_return_skb_page(PAGE2)        // drops second pp_frag_count\\n\\n(5) PAGE2 is freed, but the third RX descriptor was still using it!\\n    In our case this causes IOMMU faults, but it would silently corrupt\\n    memory if the IOMMU was disabled.\\n\\nChange the logic that checks whether pp_recycle SKBs can be coalesced.\\nWe still reject differing pp_recycle between \u0027from\u0027 and \u0027to\u0027 SKBs, but\\nin order to avoid the situation described above, we also reject\\ncoalescing when both \u0027from\u0027 and \u0027to\u0027 are pp_recycled and \u0027from\u0027 is\\ncloned.\\n\\nThe new logic allows coalescing a cloned pp_recycle SKB into a page\\nrefcounted one, because in this case the release (4) will drop the right\\nreference, the one taken by skb_try_coalesce().\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.34\", \"versionStartIncluding\": \"5.15\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.16.20\", \"versionStartIncluding\": \"5.15\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.17.3\", \"versionStartIncluding\": \"5.15\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.18\", \"versionStartIncluding\": \"5.15\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T08:53:53.011Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2022-49093\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T08:53:53.011Z\", \"dateReserved\": \"2025-02-26T01:49:39.249Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2025-02-26T01:54:47.669Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.