Vulnerability-Lookup

GHSA-F5PV-Q555-4V9F

Vulnerability from github – Published: 2025-12-08 03:31 – Updated: 2025-12-08 03:31

Details

In the Linux kernel, the following vulnerability has been resolved:

drm/gud: Fix UBSAN warning

UBSAN complains about invalid value for bool:

[ 101.165172] [drm] Initialized gud 1.0.0 20200422 for 2-3.2:1.0 on minor 1 [ 101.213360] gud 2-3.2:1.0: [drm] fb1: guddrmfb frame buffer device [ 101.213426] usbcore: registered new interface driver gud [ 101.989431] ================================================================================ [ 101.989441] UBSAN: invalid-load in linux/include/linux/iosys-map.h:253:9 [ 101.989447] load of value 121 is not a valid value for type '_Bool' [ 101.989451] CPU: 1 PID: 455 Comm: kworker/1:6 Not tainted 5.18.0-rc5-gud-5.18-rc5 #3 [ 101.989456] Hardware name: Hewlett-Packard HP EliteBook 820 G1/1991, BIOS L71 Ver. 01.44 04/12/2018 [ 101.989459] Workqueue: events_long gud_flush_work [gud] [ 101.989471] Call Trace: [ 101.989474] [ 101.989479] dump_stack_lvl+0x49/0x5f [ 101.989488] dump_stack+0x10/0x12 [ 101.989493] ubsan_epilogue+0x9/0x3b [ 101.989498] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [ 101.989504] dma_buf_vmap.cold+0x38/0x3d [ 101.989511] ? find_busiest_group+0x48/0x300 [ 101.989520] drm_gem_shmem_vmap+0x76/0x1b0 [drm_shmem_helper] [ 101.989528] drm_gem_shmem_object_vmap+0x9/0xb [drm_shmem_helper] [ 101.989535] drm_gem_vmap+0x26/0x60 [drm] [ 101.989594] drm_gem_fb_vmap+0x47/0x150 [drm_kms_helper] [ 101.989630] gud_prep_flush+0xc1/0x710 [gud] [ 101.989639] ? _raw_spin_lock+0x17/0x40 [ 101.989648] gud_flush_work+0x1e0/0x430 [gud] [ 101.989653] ? __switch_to+0x11d/0x470 [ 101.989664] process_one_work+0x21f/0x3f0 [ 101.989673] worker_thread+0x200/0x3e0 [ 101.989679] ? rescuer_thread+0x390/0x390 [ 101.989684] kthread+0xfd/0x130 [ 101.989690] ? kthread_complete_and_exit+0x20/0x20 [ 101.989696] ret_from_fork+0x22/0x30 [ 101.989706] [ 101.989708] ================================================================================

The source of this warning is in iosys_map_clear() called from dma_buf_vmap(). It conditionally sets values based on map->is_iomem. The iosys_map variables are allocated uninitialized on the stack leading to ->is_iomem having all kinds of values and not only 0/1.

Fix this by zeroing the iosys_map variables.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2022-50628"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-08T02:15:48Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/gud: Fix UBSAN warning\n\nUBSAN complains about invalid value for bool:\n\n[  101.165172] [drm] Initialized gud 1.0.0 20200422 for 2-3.2:1.0 on minor 1\n[  101.213360] gud 2-3.2:1.0: [drm] fb1: guddrmfb frame buffer device\n[  101.213426] usbcore: registered new interface driver gud\n[  101.989431] ================================================================================\n[  101.989441] UBSAN: invalid-load in linux/include/linux/iosys-map.h:253:9\n[  101.989447] load of value 121 is not a valid value for type \u0027_Bool\u0027\n[  101.989451] CPU: 1 PID: 455 Comm: kworker/1:6 Not tainted 5.18.0-rc5-gud-5.18-rc5 #3\n[  101.989456] Hardware name: Hewlett-Packard HP EliteBook 820 G1/1991, BIOS L71 Ver. 01.44 04/12/2018\n[  101.989459] Workqueue: events_long gud_flush_work [gud]\n[  101.989471] Call Trace:\n[  101.989474]  \u003cTASK\u003e\n[  101.989479]  dump_stack_lvl+0x49/0x5f\n[  101.989488]  dump_stack+0x10/0x12\n[  101.989493]  ubsan_epilogue+0x9/0x3b\n[  101.989498]  __ubsan_handle_load_invalid_value.cold+0x44/0x49\n[  101.989504]  dma_buf_vmap.cold+0x38/0x3d\n[  101.989511]  ? find_busiest_group+0x48/0x300\n[  101.989520]  drm_gem_shmem_vmap+0x76/0x1b0 [drm_shmem_helper]\n[  101.989528]  drm_gem_shmem_object_vmap+0x9/0xb [drm_shmem_helper]\n[  101.989535]  drm_gem_vmap+0x26/0x60 [drm]\n[  101.989594]  drm_gem_fb_vmap+0x47/0x150 [drm_kms_helper]\n[  101.989630]  gud_prep_flush+0xc1/0x710 [gud]\n[  101.989639]  ? _raw_spin_lock+0x17/0x40\n[  101.989648]  gud_flush_work+0x1e0/0x430 [gud]\n[  101.989653]  ? __switch_to+0x11d/0x470\n[  101.989664]  process_one_work+0x21f/0x3f0\n[  101.989673]  worker_thread+0x200/0x3e0\n[  101.989679]  ? rescuer_thread+0x390/0x390\n[  101.989684]  kthread+0xfd/0x130\n[  101.989690]  ? kthread_complete_and_exit+0x20/0x20\n[  101.989696]  ret_from_fork+0x22/0x30\n[  101.989706]  \u003c/TASK\u003e\n[  101.989708] ================================================================================\n\nThe source of this warning is in iosys_map_clear() called from\ndma_buf_vmap(). It conditionally sets values based on map-\u003eis_iomem. The\niosys_map variables are allocated uninitialized on the stack leading to\n-\u003eis_iomem having all kinds of values and not only 0/1.\n\nFix this by zeroing the iosys_map variables.",
  "id": "GHSA-f5pv-q555-4v9f",
  "modified": "2025-12-08T03:31:03Z",
  "published": "2025-12-08T03:31:03Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50628"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/832f861a46039d50536dcfda0a9fb334b48d0f8b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/951df98024f7272f85df5044eca7374f5b5b24ef"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e1078b270d218f8d58efb4d78ea25a4d16ba3490"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2022-50628 (GCVE-0-2022-50628)

Vulnerability from cvelistv5 – Published: 2025-12-08 01:16 – Updated: 2026-05-11 19:22

Title

drm/gud: Fix UBSAN warning

Summary

In the Linux kernel, the following vulnerability has been resolved: drm/gud: Fix UBSAN warning UBSAN complains about invalid value for bool: [ 101.165172] [drm] Initialized gud 1.0.0 20200422 for 2-3.2:1.0 on minor 1 [ 101.213360] gud 2-3.2:1.0: [drm] fb1: guddrmfb frame buffer device [ 101.213426] usbcore: registered new interface driver gud [ 101.989431] ================================================================================ [ 101.989441] UBSAN: invalid-load in linux/include/linux/iosys-map.h:253:9 [ 101.989447] load of value 121 is not a valid value for type '_Bool' [ 101.989451] CPU: 1 PID: 455 Comm: kworker/1:6 Not tainted 5.18.0-rc5-gud-5.18-rc5 #3 [ 101.989456] Hardware name: Hewlett-Packard HP EliteBook 820 G1/1991, BIOS L71 Ver. 01.44 04/12/2018 [ 101.989459] Workqueue: events_long gud_flush_work [gud] [ 101.989471] Call Trace: [ 101.989474] <TASK> [ 101.989479] dump_stack_lvl+0x49/0x5f [ 101.989488] dump_stack+0x10/0x12 [ 101.989493] ubsan_epilogue+0x9/0x3b [ 101.989498] __ubsan_handle_load_invalid_value.cold+0x44/0x49 [ 101.989504] dma_buf_vmap.cold+0x38/0x3d [ 101.989511] ? find_busiest_group+0x48/0x300 [ 101.989520] drm_gem_shmem_vmap+0x76/0x1b0 [drm_shmem_helper] [ 101.989528] drm_gem_shmem_object_vmap+0x9/0xb [drm_shmem_helper] [ 101.989535] drm_gem_vmap+0x26/0x60 [drm] [ 101.989594] drm_gem_fb_vmap+0x47/0x150 [drm_kms_helper] [ 101.989630] gud_prep_flush+0xc1/0x710 [gud] [ 101.989639] ? _raw_spin_lock+0x17/0x40 [ 101.989648] gud_flush_work+0x1e0/0x430 [gud] [ 101.989653] ? __switch_to+0x11d/0x470 [ 101.989664] process_one_work+0x21f/0x3f0 [ 101.989673] worker_thread+0x200/0x3e0 [ 101.989679] ? rescuer_thread+0x390/0x390 [ 101.989684] kthread+0xfd/0x130 [ 101.989690] ? kthread_complete_and_exit+0x20/0x20 [ 101.989696] ret_from_fork+0x22/0x30 [ 101.989706] </TASK> [ 101.989708] ================================================================================ The source of this warning is in iosys_map_clear() called from dma_buf_vmap(). It conditionally sets values based on map->is_iomem. The iosys_map variables are allocated uninitialized on the stack leading to ->is_iomem having all kinds of values and not only 0/1. Fix this by zeroing the iosys_map variables.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

3 references

URL	Tags
https://git.kernel.org/stable/c/832f861a46039d505…
https://git.kernel.org/stable/c/e1078b270d218f8d5…
https://git.kernel.org/stable/c/951df98024f7272f8…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 , < 832f861a46039d50536dcfda0a9fb334b48d0f8b (git) Affected: 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 , < e1078b270d218f8d58efb4d78ea25a4d16ba3490 (git) Affected: 40e1a70b4aedf2859a1829991b48ef0ebe650bf2 , < 951df98024f7272f85df5044eca7374f5b5b24ef (git)
Linux	Linux	Affected: 5.13 Unaffected: 0 , < 5.13 (semver) Unaffected: 6.1.16 , ≤ 6.1.* (semver) Unaffected: 6.2.3 , ≤ 6.2.* (semver) Unaffected: 6.3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/gud/gud_pipe.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "832f861a46039d50536dcfda0a9fb334b48d0f8b",
              "status": "affected",
              "version": "40e1a70b4aedf2859a1829991b48ef0ebe650bf2",
              "versionType": "git"
            },
            {
              "lessThan": "e1078b270d218f8d58efb4d78ea25a4d16ba3490",
              "status": "affected",
              "version": "40e1a70b4aedf2859a1829991b48ef0ebe650bf2",
              "versionType": "git"
            },
            {
              "lessThan": "951df98024f7272f85df5044eca7374f5b5b24ef",
              "status": "affected",
              "version": "40e1a70b4aedf2859a1829991b48ef0ebe650bf2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/gud/gud_pipe.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.13"
            },
            {
              "lessThan": "5.13",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.16",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.2.*",
              "status": "unaffected",
              "version": "6.2.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.16",
                  "versionStartIncluding": "5.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.2.3",
                  "versionStartIncluding": "5.13",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.3",
                  "versionStartIncluding": "5.13",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/gud: Fix UBSAN warning\n\nUBSAN complains about invalid value for bool:\n\n[  101.165172] [drm] Initialized gud 1.0.0 20200422 for 2-3.2:1.0 on minor 1\n[  101.213360] gud 2-3.2:1.0: [drm] fb1: guddrmfb frame buffer device\n[  101.213426] usbcore: registered new interface driver gud\n[  101.989431] ================================================================================\n[  101.989441] UBSAN: invalid-load in linux/include/linux/iosys-map.h:253:9\n[  101.989447] load of value 121 is not a valid value for type \u0027_Bool\u0027\n[  101.989451] CPU: 1 PID: 455 Comm: kworker/1:6 Not tainted 5.18.0-rc5-gud-5.18-rc5 #3\n[  101.989456] Hardware name: Hewlett-Packard HP EliteBook 820 G1/1991, BIOS L71 Ver. 01.44 04/12/2018\n[  101.989459] Workqueue: events_long gud_flush_work [gud]\n[  101.989471] Call Trace:\n[  101.989474]  \u003cTASK\u003e\n[  101.989479]  dump_stack_lvl+0x49/0x5f\n[  101.989488]  dump_stack+0x10/0x12\n[  101.989493]  ubsan_epilogue+0x9/0x3b\n[  101.989498]  __ubsan_handle_load_invalid_value.cold+0x44/0x49\n[  101.989504]  dma_buf_vmap.cold+0x38/0x3d\n[  101.989511]  ? find_busiest_group+0x48/0x300\n[  101.989520]  drm_gem_shmem_vmap+0x76/0x1b0 [drm_shmem_helper]\n[  101.989528]  drm_gem_shmem_object_vmap+0x9/0xb [drm_shmem_helper]\n[  101.989535]  drm_gem_vmap+0x26/0x60 [drm]\n[  101.989594]  drm_gem_fb_vmap+0x47/0x150 [drm_kms_helper]\n[  101.989630]  gud_prep_flush+0xc1/0x710 [gud]\n[  101.989639]  ? _raw_spin_lock+0x17/0x40\n[  101.989648]  gud_flush_work+0x1e0/0x430 [gud]\n[  101.989653]  ? __switch_to+0x11d/0x470\n[  101.989664]  process_one_work+0x21f/0x3f0\n[  101.989673]  worker_thread+0x200/0x3e0\n[  101.989679]  ? rescuer_thread+0x390/0x390\n[  101.989684]  kthread+0xfd/0x130\n[  101.989690]  ? kthread_complete_and_exit+0x20/0x20\n[  101.989696]  ret_from_fork+0x22/0x30\n[  101.989706]  \u003c/TASK\u003e\n[  101.989708] ================================================================================\n\nThe source of this warning is in iosys_map_clear() called from\ndma_buf_vmap(). It conditionally sets values based on map-\u003eis_iomem. The\niosys_map variables are allocated uninitialized on the stack leading to\n-\u003eis_iomem having all kinds of values and not only 0/1.\n\nFix this by zeroing the iosys_map variables."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T19:22:31.598Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/832f861a46039d50536dcfda0a9fb334b48d0f8b"
        },
        {
          "url": "https://git.kernel.org/stable/c/e1078b270d218f8d58efb4d78ea25a4d16ba3490"
        },
        {
          "url": "https://git.kernel.org/stable/c/951df98024f7272f85df5044eca7374f5b5b24ef"
        }
      ],
      "title": "drm/gud: Fix UBSAN warning",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-50628",
    "datePublished": "2025-12-08T01:16:43.390Z",
    "dateReserved": "2025-12-08T01:14:55.191Z",
    "dateUpdated": "2026-05-11T19:22:31.598Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.