CVE-2025-21933 (GCVE-0-2025-21933)
Vulnerability from cvelistv5
Published
2025-04-01 15:41
Modified
2025-05-04 07:24
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: arm: pgtable: fix NULL pointer dereference issue When update_mmu_cache_range() is called by update_mmu_cache(), the vmf parameter is NULL, which will cause a NULL pointer dereference issue in adjust_pte(): Unable to handle kernel NULL pointer dereference at virtual address 00000030 when read Hardware name: Atmel AT91SAM9 PC is at update_mmu_cache_range+0x1e0/0x278 LR is at pte_offset_map_rw_nolock+0x18/0x2c Call trace: update_mmu_cache_range from remove_migration_pte+0x29c/0x2ec remove_migration_pte from rmap_walk_file+0xcc/0x130 rmap_walk_file from remove_migration_ptes+0x90/0xa4 remove_migration_ptes from migrate_pages_batch+0x6d4/0x858 migrate_pages_batch from migrate_pages+0x188/0x488 migrate_pages from compact_zone+0x56c/0x954 compact_zone from compact_node+0x90/0xf0 compact_node from kcompactd+0x1d4/0x204 kcompactd from kthread+0x120/0x12c kthread from ret_from_fork+0x14/0x38 Exception stack(0xc0d8bfb0 to 0xc0d8bff8) To fix it, do not rely on whether 'ptl' is equal to decide whether to hold the pte lock, but decide it by whether CONFIG_SPLIT_PTE_PTLOCKS is enabled. In addition, if two vmas map to the same PTE page, there is no need to hold the pte lock again, otherwise a deadlock will occur. Just add the need_lock parameter to let adjust_pte() know this information.
References
Impacted products
Vendor Product Version
Linux Linux Version: fc9c45b71f43cafcc0435dd4c7a2d3b99955a0fa
Version: fc9c45b71f43cafcc0435dd4c7a2d3b99955a0fa
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/arm/mm/fault-armv.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "91d011efe30aedde067ce6d218d521cf99b162e5",
              "status": "affected",
              "version": "fc9c45b71f43cafcc0435dd4c7a2d3b99955a0fa",
              "versionType": "git"
            },
            {
              "lessThan": "a564ccfe300fa6a065beda06ab7f3c140d6b4d63",
              "status": "affected",
              "version": "fc9c45b71f43cafcc0435dd4c7a2d3b99955a0fa",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/arm/mm/fault-armv.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.13"
            },
            {
              "lessThan": "6.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.7",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14",
                  "versionStartIncluding": "6.13",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm: pgtable: fix NULL pointer dereference issue\n\nWhen update_mmu_cache_range() is called by update_mmu_cache(), the vmf\nparameter is NULL, which will cause a NULL pointer dereference issue in\nadjust_pte():\n\nUnable to handle kernel NULL pointer dereference at virtual address 00000030 when read\nHardware name: Atmel AT91SAM9\nPC is at update_mmu_cache_range+0x1e0/0x278\nLR is at pte_offset_map_rw_nolock+0x18/0x2c\nCall trace:\n update_mmu_cache_range from remove_migration_pte+0x29c/0x2ec\n remove_migration_pte from rmap_walk_file+0xcc/0x130\n rmap_walk_file from remove_migration_ptes+0x90/0xa4\n remove_migration_ptes from migrate_pages_batch+0x6d4/0x858\n migrate_pages_batch from migrate_pages+0x188/0x488\n migrate_pages from compact_zone+0x56c/0x954\n compact_zone from compact_node+0x90/0xf0\n compact_node from kcompactd+0x1d4/0x204\n kcompactd from kthread+0x120/0x12c\n kthread from ret_from_fork+0x14/0x38\nException stack(0xc0d8bfb0 to 0xc0d8bff8)\n\nTo fix it, do not rely on whether \u0027ptl\u0027 is equal to decide whether to hold\nthe pte lock, but decide it by whether CONFIG_SPLIT_PTE_PTLOCKS is\nenabled.  In addition, if two vmas map to the same PTE page, there is no\nneed to hold the pte lock again, otherwise a deadlock will occur.  Just\nadd the need_lock parameter to let adjust_pte() know this information."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-04T07:24:52.482Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/91d011efe30aedde067ce6d218d521cf99b162e5"
        },
        {
          "url": "https://git.kernel.org/stable/c/a564ccfe300fa6a065beda06ab7f3c140d6b4d63"
        }
      ],
      "title": "arm: pgtable: fix NULL pointer dereference issue",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-21933",
    "datePublished": "2025-04-01T15:41:02.300Z",
    "dateReserved": "2024-12-29T08:45:45.789Z",
    "dateUpdated": "2025-05-04T07:24:52.482Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-21933\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-04-01T16:15:24.143\",\"lastModified\":\"2025-04-10T18:06:52.953\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\narm: pgtable: fix NULL pointer dereference issue\\n\\nWhen update_mmu_cache_range() is called by update_mmu_cache(), the vmf\\nparameter is NULL, which will cause a NULL pointer dereference issue in\\nadjust_pte():\\n\\nUnable to handle kernel NULL pointer dereference at virtual address 00000030 when read\\nHardware name: Atmel AT91SAM9\\nPC is at update_mmu_cache_range+0x1e0/0x278\\nLR is at pte_offset_map_rw_nolock+0x18/0x2c\\nCall trace:\\n update_mmu_cache_range from remove_migration_pte+0x29c/0x2ec\\n remove_migration_pte from rmap_walk_file+0xcc/0x130\\n rmap_walk_file from remove_migration_ptes+0x90/0xa4\\n remove_migration_ptes from migrate_pages_batch+0x6d4/0x858\\n migrate_pages_batch from migrate_pages+0x188/0x488\\n migrate_pages from compact_zone+0x56c/0x954\\n compact_zone from compact_node+0x90/0xf0\\n compact_node from kcompactd+0x1d4/0x204\\n kcompactd from kthread+0x120/0x12c\\n kthread from ret_from_fork+0x14/0x38\\nException stack(0xc0d8bfb0 to 0xc0d8bff8)\\n\\nTo fix it, do not rely on whether \u0027ptl\u0027 is equal to decide whether to hold\\nthe pte lock, but decide it by whether CONFIG_SPLIT_PTE_PTLOCKS is\\nenabled.  In addition, if two vmas map to the same PTE page, there is no\\nneed to hold the pte lock again, otherwise a deadlock will occur.  Just\\nadd the need_lock parameter to let adjust_pte() know this information.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: arm: pgtable: corregir problema de desreferencia de puntero NULL Cuando update_mmu_cache_range() es llamado por update_mmu_cache(), el par\u00e1metro vmf es NULL, lo que causar\u00e1 un problema de desreferencia de puntero NULL en adjust_pte(): No se puede gestionar la desreferencia de puntero NULL del kernel en la direcci\u00f3n virtual 00000030 cuando se lee Nombre del hardware: Atmel AT91SAM9 La PC est\u00e1 en update_mmu_cache_range+0x1e0/0x278 LR est\u00e1 en pte_offset_map_rw_nolock+0x18/0x2c Rastreo de llamadas: update_mmu_cache_range de remove_migration_pte+0x29c/0x2ec remove_migration_pte de rmap_walk_file+0xcc/0x130 rmap_walk_file de remove_migration_ptes+0x90/0xa4 remove_migration_ptes de migration_pages_batch+0x6d4/0x858 migration_pages_batch de migration_pages+0x188/0x488 migration_pages de compact_zone+0x56c/0x954 compact_zone de compact_node+0x90/0xf0 compact_node de kcompactd+0x1d4/0x204 kcompactd de kthread+0x120/0x12c kthread de ret_from_fork+0x14/0x38 Pila de excepciones (0xc0d8bfb0 a 0xc0d8bff8) Para solucionarlo, no conf\u00ede en si \u0027ptl\u0027 es igual para decidir si mantener el bloqueo pte, sino dec\u00eddalo en funci\u00f3n de si CONFIG_SPLIT_PTE_PTLOCKS est\u00e1 habilitado. Adem\u00e1s, si dos m\u00e1quinas virtuales asignan a la misma p\u00e1gina PTE, no es necesario volver a bloquear la p\u00e1gina PTE; de lo contrario, se producir\u00e1 un bloqueo. Simplemente agregue el par\u00e1metro need_lock para que adjust_pte() conozca esta informaci\u00f3n.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-476\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.13\",\"versionEndExcluding\":\"6.13.7\",\"matchCriteriaId\":\"842F5A44-3E71-4546-B4FD-43B0ACE3F32B\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"186716B6-2B66-4BD0-852E-D48E71C0C85F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"0D3E781C-403A-498F-9DA9-ECEE50F41E75\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"66619FB8-0AAF-4166-B2CF-67B24143261D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"D3D6550E-6679-4560-902D-AF52DCFE905B\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.14:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"45B90F6B-BEC7-4D4E-883A-9DBADE021750\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/91d011efe30aedde067ce6d218d521cf99b162e5\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a564ccfe300fa6a065beda06ab7f3c140d6b4d63\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.