idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
38,783 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void __munlock_isolated_page(struct page *page)
{
int ret = SWAP_AGAIN;
/*
* Optimization: if the page was mapped just once, that's our mapping
* and we don't need to check all the other vmas.
*/
if (page_mapcount(page) > 1)
ret = try_to_munlock(page);
/* Did try_to_unlock() succeed or punt? */
if... | 22,334,080,912,643,270,000,000,000,000,000,000,000 | mlock.c | 150,601,957,285,814,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,784 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void __munlock_isolation_failed(struct page *page)
{
if (PageUnevictable(page))
__count_vm_event(UNEVICTABLE_PGSTRANDED);
else
__count_vm_event(UNEVICTABLE_PGMUNLOCKED);
}
| 178,984,011,829,944,840,000,000,000,000,000,000,000 | mlock.c | 296,885,345,766,349,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,785 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void __munlock_pagevec(struct pagevec *pvec, struct zone *zone)
{
int i;
int nr = pagevec_count(pvec);
int delta_munlocked;
struct pagevec pvec_putback;
int pgrescued = 0;
pagevec_init(&pvec_putback, 0);
/* Phase 1: page isolation */
spin_lock_irq(&zone->lru_lock);
for (i = 0; i < nr; i++) {
struct ... | 242,279,928,338,794,050,000,000,000,000,000,000,000 | mlock.c | 150,601,957,285,814,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,786 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static unsigned long __munlock_pagevec_fill(struct pagevec *pvec,
struct vm_area_struct *vma, int zoneid, unsigned long start,
unsigned long end)
{
pte_t *pte;
spinlock_t *ptl;
/*
* Initialize pte walk starting at the already pinned page where we
* are sure that there is a pte, as it was pinned under the sa... | 122,537,767,236,430,560,000,000,000,000,000,000,000 | mlock.c | 150,601,957,285,814,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,787 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void __putback_lru_fast(struct pagevec *pvec, int pgrescued)
{
count_vm_events(UNEVICTABLE_PGMUNLOCKED, pagevec_count(pvec));
/*
*__pagevec_lru_add() calls release_pages() so we don't call
* put_page() explicitly
*/
__pagevec_lru_add(pvec);
count_vm_events(UNEVICTABLE_PGRESCUED, pgrescued);
}
| 92,151,081,961,006,040,000,000,000,000,000,000,000 | mlock.c | 296,885,345,766,349,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,788 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static bool __putback_lru_fast_prepare(struct page *page, struct pagevec *pvec,
int *pgrescued)
{
VM_BUG_ON_PAGE(PageLRU(page), page);
VM_BUG_ON_PAGE(!PageLocked(page), page);
if (page_mapcount(page) <= 1 && page_evictable(page)) {
pagevec_add(pvec, page);
if (TestClearPageUnevictable(page))
(*pgrescued)++... | 244,007,703,271,288,240,000,000,000,000,000,000,000 | mlock.c | 296,885,345,766,349,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,789 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int can_do_mlock(void)
{
if (capable(CAP_IPC_LOCK))
return 1;
if (rlimit(RLIMIT_MEMLOCK) != 0)
return 1;
return 0;
}
| 315,797,023,309,995,470,000,000,000,000,000,000,000 | mlock.c | 150,601,957,285,814,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,790 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void clear_page_mlock(struct page *page)
{
if (!TestClearPageMlocked(page))
return;
mod_zone_page_state(page_zone(page), NR_MLOCK,
-hpage_nr_pages(page));
count_vm_event(UNEVICTABLE_PGCLEARED);
if (!isolate_lru_page(page)) {
putback_lru_page(page);
} else {
/*
* We lost the race. the page already ... | 33,659,589,196,556,890,000,000,000,000,000,000,000 | mlock.c | 296,885,345,766,349,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,791 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static int do_mlockall(int flags)
{
struct vm_area_struct * vma, * prev = NULL;
if (flags & MCL_FUTURE)
current->mm->def_flags |= VM_LOCKED;
else
current->mm->def_flags &= ~VM_LOCKED;
if (flags == MCL_FUTURE)
goto out;
for (vma = current->mm->mmap; vma ; vma = prev->vm_next) {
vm_flags_t newflags;
new... | 226,486,258,741,441,760,000,000,000,000,000,000,000 | mlock.c | 150,601,957,285,814,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,792 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static int mlock_fixup(struct vm_area_struct *vma, struct vm_area_struct **prev,
unsigned long start, unsigned long end, vm_flags_t newflags)
{
struct mm_struct *mm = vma->vm_mm;
pgoff_t pgoff;
int nr_pages;
int ret = 0;
int lock = !!(newflags & VM_LOCKED);
if (newflags == vma->vm_flags || (vma->vm_flags & VM_S... | 181,664,559,613,298,100,000,000,000,000,000,000,000 | mlock.c | 150,601,957,285,814,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,793 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void munlock_vma_pages_range(struct vm_area_struct *vma,
unsigned long start, unsigned long end)
{
vma->vm_flags &= ~VM_LOCKED;
while (start < end) {
struct page *page = NULL;
unsigned int page_mask;
unsigned long page_increm;
struct pagevec pvec;
struct zone *zone;
int zoneid;
pagevec_init(&p... | 307,536,805,275,801,130,000,000,000,000,000,000,000 | mlock.c | 150,601,957,285,814,880,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,794 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void user_shm_unlock(size_t size, struct user_struct *user)
{
spin_lock(&shmlock_user_lock);
user->locked_shm -= (size + PAGE_SIZE - 1) >> PAGE_SHIFT;
spin_unlock(&shmlock_user_lock);
free_uid(user);
}
| 257,141,816,820,805,030,000,000,000,000,000,000,000 | mlock.c | 296,885,345,766,349,730,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,795 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void __hugepage_set_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address, int exclusive)
{
struct anon_vma *anon_vma = vma->anon_vma;
BUG_ON(!anon_vma);
if (PageAnon(page))
return;
if (!exclusive)
anon_vma = anon_vma->root;
anon_vma = (void *) anon_vma + PAGE_MAPPING_ANON;
... | 143,930,539,594,522,000,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,796 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void __page_check_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address)
{
#ifdef CONFIG_DEBUG_VM
/*
* The page's anon-rmap details (mapping and index) are guaranteed to
* be set up correctly at this point.
*
* We have exclusion against page_add_anon_rmap because the caller
*... | 205,152,008,524,153,130,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,797 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void __page_set_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address, int exclusive)
{
struct anon_vma *anon_vma = vma->anon_vma;
BUG_ON(!anon_vma);
if (PageAnon(page))
return;
/*
* If the page isn't exclusively mapped into this vma,
* we must use the _oldest_ possible ano... | 280,286,262,357,245,780,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,798 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void __put_anon_vma(struct anon_vma *anon_vma)
{
struct anon_vma *root = anon_vma->root;
if (root != anon_vma && atomic_dec_and_test(&root->refcount))
anon_vma_free(root);
anon_vma_free(anon_vma);
}
| 71,618,876,464,893,630,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,799 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | __vma_address(struct page *page, struct vm_area_struct *vma)
{
pgoff_t pgoff = page->index << (PAGE_CACHE_SHIFT - PAGE_SHIFT);
if (unlikely(is_vm_hugetlb_page(vma)))
pgoff = page->index << huge_page_order(page_hstate(page));
return vma->vm_start + ((pgoff - vma->vm_pgoff) << PAGE_SHIFT);
}
| 131,207,252,017,072,960,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,800 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static inline struct anon_vma *anon_vma_alloc(void)
{
struct anon_vma *anon_vma;
anon_vma = kmem_cache_alloc(anon_vma_cachep, GFP_KERNEL);
if (anon_vma) {
atomic_set(&anon_vma->refcount, 1);
/*
* Initialise the anon_vma root to point to itself. If called
* from fork, the root will be reset to the parents ... | 317,734,295,052,575,100,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,801 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static inline struct anon_vma_chain *anon_vma_chain_alloc(gfp_t gfp)
{
return kmem_cache_alloc(anon_vma_chain_cachep, gfp);
}
| 200,701,462,967,765,300,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,802 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void anon_vma_chain_free(struct anon_vma_chain *anon_vma_chain)
{
kmem_cache_free(anon_vma_chain_cachep, anon_vma_chain);
}
| 114,376,826,440,958,870,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,803 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void anon_vma_chain_link(struct vm_area_struct *vma,
struct anon_vma_chain *avc,
struct anon_vma *anon_vma)
{
avc->vma = vma;
avc->anon_vma = anon_vma;
list_add(&avc->same_vma, &vma->anon_vma_chain);
anon_vma_interval_tree_insert(avc, &anon_vma->rb_root);
}
| 14,275,952,755,815,770,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,804 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int anon_vma_clone(struct vm_area_struct *dst, struct vm_area_struct *src)
{
struct anon_vma_chain *avc, *pavc;
struct anon_vma *root = NULL;
list_for_each_entry_reverse(pavc, &src->anon_vma_chain, same_vma) {
struct anon_vma *anon_vma;
avc = anon_vma_chain_alloc(GFP_NOWAIT | __GFP_NOWARN);
if (unlikely(!avc... | 254,563,000,320,730,960,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,805 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static void anon_vma_ctor(void *data)
{
struct anon_vma *anon_vma = data;
init_rwsem(&anon_vma->rwsem);
atomic_set(&anon_vma->refcount, 0);
anon_vma->rb_root = RB_ROOT;
}
| 143,381,658,112,515,840,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,806 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int anon_vma_fork(struct vm_area_struct *vma, struct vm_area_struct *pvma)
{
struct anon_vma_chain *avc;
struct anon_vma *anon_vma;
/* Don't bother if the parent process has no anon_vma here. */
if (!pvma->anon_vma)
return 0;
/*
* First, attach the new VMA to the parent VMA's anon_vmas,
* so rmap can find ... | 150,788,616,563,148,200,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,807 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static inline void anon_vma_free(struct anon_vma *anon_vma)
{
VM_BUG_ON(atomic_read(&anon_vma->refcount));
/*
* Synchronize against page_lock_anon_vma_read() such that
* we can safely hold the lock without the anon_vma getting
* freed.
*
* Relies on the full mb implied by the atomic_dec_and_test() from
*... | 160,129,987,725,434,900,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,808 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void __init anon_vma_init(void)
{
anon_vma_cachep = kmem_cache_create("anon_vma", sizeof(struct anon_vma),
0, SLAB_DESTROY_BY_RCU|SLAB_PANIC, anon_vma_ctor);
anon_vma_chain_cachep = KMEM_CACHE(anon_vma_chain, SLAB_PANIC);
}
| 231,114,915,816,177,160,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,809 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int anon_vma_prepare(struct vm_area_struct *vma)
{
struct anon_vma *anon_vma = vma->anon_vma;
struct anon_vma_chain *avc;
might_sleep();
if (unlikely(!anon_vma)) {
struct mm_struct *mm = vma->vm_mm;
struct anon_vma *allocated;
avc = anon_vma_chain_alloc(GFP_KERNEL);
if (!avc)
goto out_enomem;
anon_v... | 283,449,607,946,673,630,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,810 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void do_page_add_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address, int exclusive)
{
int first = atomic_inc_and_test(&page->_mapcount);
if (first) {
if (PageTransHuge(page))
__inc_zone_page_state(page,
NR_ANON_TRANSPARENT_HUGEPAGES);
__mod_zone_page_state(page_zone(page... | 220,985,444,093,433,500,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,811 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void hugepage_add_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address)
{
struct anon_vma *anon_vma = vma->anon_vma;
int first;
BUG_ON(!PageLocked(page));
BUG_ON(!anon_vma);
/* address might be in next vma when migration races vma_adjust */
first = atomic_inc_and_test(&page->_map... | 199,251,621,044,485,080,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,812 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void hugepage_add_new_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address)
{
BUG_ON(address < vma->vm_start || address >= vma->vm_end);
atomic_set(&page->_mapcount, 0);
__hugepage_set_anon_rmap(page, vma, address, 1);
}
| 154,365,181,353,390,050,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,813 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static bool invalid_migration_vma(struct vm_area_struct *vma, void *arg)
{
return is_vma_temporary_stack(vma);
}
| 271,333,373,406,409,830,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,814 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static bool invalid_mkclean_vma(struct vm_area_struct *vma, void *arg)
{
if (vma->vm_flags & VM_SHARED)
return false;
return true;
}
| 193,965,015,434,367,820,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,815 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static bool invalid_page_referenced_vma(struct vm_area_struct *vma, void *arg)
{
struct page_referenced_arg *pra = arg;
struct mem_cgroup *memcg = pra->memcg;
if (!mm_match_cgroup(vma->vm_mm, memcg))
return true;
return false;
}
| 174,719,554,733,064,800,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,816 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | bool is_vma_temporary_stack(struct vm_area_struct *vma)
{
int maybe_stack = vma->vm_flags & (VM_GROWSDOWN | VM_GROWSUP);
if (!maybe_stack)
return false;
if ((vma->vm_flags & VM_STACK_INCOMPLETE_SETUP) ==
VM_STACK_INCOMPLETE_SETUP)
return true;
return false;
}
| 103,100,225,345,418,830,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,817 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static inline struct anon_vma *lock_anon_vma_root(struct anon_vma *root, struct anon_vma *anon_vma)
{
struct anon_vma *new_root = anon_vma->root;
if (new_root != root) {
if (WARN_ON_ONCE(root))
up_write(&root->rwsem);
root = new_root;
down_write(&root->rwsem);
}
return root;
}
| 161,660,542,197,576,650,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,818 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | pmd_t *mm_find_pmd(struct mm_struct *mm, unsigned long address)
{
pgd_t *pgd;
pud_t *pud;
pmd_t *pmd = NULL;
pgd = pgd_offset(mm, address);
if (!pgd_present(*pgd))
goto out;
pud = pud_offset(pgd, address);
if (!pud_present(*pud))
goto out;
pmd = pmd_offset(pud, address);
if (!pmd_present(*pmd))
pmd = ... | 210,906,574,871,501,200,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,819 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void page_add_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address)
{
do_page_add_anon_rmap(page, vma, address, 0);
}
| 162,536,060,585,337,200,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,820 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void page_add_file_rmap(struct page *page)
{
bool locked;
unsigned long flags;
mem_cgroup_begin_update_page_stat(page, &locked, &flags);
if (atomic_inc_and_test(&page->_mapcount)) {
__inc_zone_page_state(page, NR_FILE_MAPPED);
mem_cgroup_inc_page_stat(page, MEM_CGROUP_STAT_FILE_MAPPED);
}
mem_cgroup_end_upda... | 38,777,168,597,110,290,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,821 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void page_add_new_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address)
{
VM_BUG_ON(address < vma->vm_start || address >= vma->vm_end);
SetPageSwapBacked(page);
atomic_set(&page->_mapcount, 0); /* increment count (starts at -1) */
if (PageTransHuge(page))
__inc_zone_page_state(page, NR_... | 187,660,845,416,012,760,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,822 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | unsigned long page_address_in_vma(struct page *page, struct vm_area_struct *vma)
{
unsigned long address;
if (PageAnon(page)) {
struct anon_vma *page__anon_vma = page_anon_vma(page);
/*
* Note: swapoff's unuse_vma() is more efficient with this
* check, and needs it to match anon_vma when KSM is active.
*... | 2,030,085,923,424,262,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,823 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | struct anon_vma *page_get_anon_vma(struct page *page)
{
struct anon_vma *anon_vma = NULL;
unsigned long anon_mapping;
rcu_read_lock();
anon_mapping = (unsigned long) ACCESS_ONCE(page->mapping);
if ((anon_mapping & PAGE_MAPPING_FLAGS) != PAGE_MAPPING_ANON)
goto out;
if (!page_mapped(page))
goto out;
anon_vm... | 612,472,931,841,216,340,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,824 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | struct anon_vma *page_lock_anon_vma_read(struct page *page)
{
struct anon_vma *anon_vma = NULL;
struct anon_vma *root_anon_vma;
unsigned long anon_mapping;
rcu_read_lock();
anon_mapping = (unsigned long) ACCESS_ONCE(page->mapping);
if ((anon_mapping & PAGE_MAPPING_FLAGS) != PAGE_MAPPING_ANON)
goto out;
if (!p... | 50,949,231,278,088,270,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,825 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int page_mapped_in_vma(struct page *page, struct vm_area_struct *vma)
{
unsigned long address;
pte_t *pte;
spinlock_t *ptl;
address = __vma_address(page, vma);
if (unlikely(address < vma->vm_start || address >= vma->vm_end))
return 0;
pte = page_check_address(page, vma->vm_mm, address, &ptl, 1);
if (!pte) /... | 214,068,550,807,143,200,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,826 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int page_mkclean(struct page *page)
{
int cleaned = 0;
struct address_space *mapping;
struct rmap_walk_control rwc = {
.arg = (void *)&cleaned,
.rmap_one = page_mkclean_one,
.invalid_vma = invalid_mkclean_vma,
};
BUG_ON(!PageLocked(page));
if (!page_mapped(page))
return 0;
mapping = page_mapping(page)... | 301,436,685,441,507,430,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,827 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static int page_mkclean_one(struct page *page, struct vm_area_struct *vma,
unsigned long address, void *arg)
{
struct mm_struct *mm = vma->vm_mm;
pte_t *pte;
spinlock_t *ptl;
int ret = 0;
int *cleaned = arg;
pte = page_check_address(page, mm, address, &ptl, 1);
if (!pte)
goto out;
if (pte_dirty(*pte)... | 37,579,196,763,298,467,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,828 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void page_move_anon_rmap(struct page *page,
struct vm_area_struct *vma, unsigned long address)
{
struct anon_vma *anon_vma = vma->anon_vma;
VM_BUG_ON_PAGE(!PageLocked(page), page);
VM_BUG_ON(!anon_vma);
VM_BUG_ON_PAGE(page->index != linear_page_index(vma, address), page);
anon_vma = (void *) anon_vma + PAGE_MAP... | 19,601,288,926,151,464,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,829 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static int page_not_mapped(struct page *page)
{
return !page_mapped(page);
};
| 206,217,104,116,108,970,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,830 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int page_referenced(struct page *page,
int is_locked,
struct mem_cgroup *memcg,
unsigned long *vm_flags)
{
int ret;
int we_locked = 0;
struct page_referenced_arg pra = {
.mapcount = page_mapcount(page),
.memcg = memcg,
};
struct rmap_walk_control rwc = {
.rmap_one = page_referenced_one,
.... | 220,205,525,008,509,800,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,831 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void page_remove_rmap(struct page *page)
{
bool anon = PageAnon(page);
bool locked;
unsigned long flags;
/*
* The anon case has no mem_cgroup page_stat to update; but may
* uncharge_page() below, where the lock ordering can deadlock if
* we hold the lock against page_stat move: so avoid it on anon.
*/
if ... | 165,414,005,624,814,280,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,832 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void page_unlock_anon_vma_read(struct anon_vma *anon_vma)
{
anon_vma_unlock_read(anon_vma);
}
| 108,675,505,205,264,860,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,833 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int rmap_walk(struct page *page, struct rmap_walk_control *rwc)
{
if (unlikely(PageKsm(page)))
return rmap_walk_ksm(page, rwc);
else if (PageAnon(page))
return rmap_walk_anon(page, rwc);
else
return rmap_walk_file(page, rwc);
}
| 334,433,189,921,958,600,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,834 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static int rmap_walk_anon(struct page *page, struct rmap_walk_control *rwc)
{
struct anon_vma *anon_vma;
pgoff_t pgoff = page->index << (PAGE_CACHE_SHIFT - PAGE_SHIFT);
struct anon_vma_chain *avc;
int ret = SWAP_AGAIN;
anon_vma = rmap_walk_anon_lock(page, rwc);
if (!anon_vma)
return ret;
anon_vma_interval_tr... | 204,199,124,748,300,230,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,835 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static struct anon_vma *rmap_walk_anon_lock(struct page *page,
struct rmap_walk_control *rwc)
{
struct anon_vma *anon_vma;
if (rwc->anon_lock)
return rwc->anon_lock(page);
/*
* Note: remove_migration_ptes() cannot use page_lock_anon_vma_read()
* because that depends on page_mapped(); but not all its usa... | 235,619,213,094,081,270,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,836 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int try_to_munlock(struct page *page)
{
int ret;
struct rmap_walk_control rwc = {
.rmap_one = try_to_unmap_one,
.arg = (void *)TTU_MUNLOCK,
.done = page_not_mapped,
/*
* We don't bother to try to find the munlocked page in
* nonlinears. It's costly. Instead, later, page reclaim logic
* may call try_t... | 256,803,237,458,556,520,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,837 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int try_to_unmap(struct page *page, enum ttu_flags flags)
{
int ret;
struct rmap_walk_control rwc = {
.rmap_one = try_to_unmap_one,
.arg = (void *)flags,
.done = page_not_mapped,
.file_nonlinear = try_to_unmap_nonlinear,
.anon_lock = page_lock_anon_vma_read,
};
VM_BUG_ON_PAGE(!PageHuge(page) && PageTrans... | 113,225,688,011,595,200,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,838 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static int try_to_unmap_nonlinear(struct page *page,
struct address_space *mapping, void *arg)
{
struct vm_area_struct *vma;
int ret = SWAP_AGAIN;
unsigned long cursor;
unsigned long max_nl_cursor = 0;
unsigned long max_nl_size = 0;
unsigned int mapcount;
list_for_each_entry(vma,
&mapping->i_mmap_nonlinear,... | 292,682,657,953,011,400,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,839 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | int try_to_unmap_one(struct page *page, struct vm_area_struct *vma,
unsigned long address, void *arg)
{
struct mm_struct *mm = vma->vm_mm;
pte_t *pte;
pte_t pteval;
spinlock_t *ptl;
int ret = SWAP_AGAIN;
enum ttu_flags flags = (enum ttu_flags)arg;
pte = page_check_address(page, mm, address, &ptl, 0);
if... | 25,017,265,930,044,316,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,840 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | void unlink_anon_vmas(struct vm_area_struct *vma)
{
struct anon_vma_chain *avc, *next;
struct anon_vma *root = NULL;
/*
* Unlink each anon_vma chained to the VMA. This list is ordered
* from newest to oldest, ensuring the root anon_vma gets freed last.
*/
list_for_each_entry_safe(avc, next, &vma->anon_vma_c... | 298,791,170,870,151,470,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,841 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | static inline void unlock_anon_vma_root(struct anon_vma *root)
{
if (root)
up_write(&root->rwsem);
}
| 333,861,219,078,605,300,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,842 | linux | 57e68e9cd65b4b8eb4045a1e0d0746458502554c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/57e68e9cd65b4b8eb4045a1e0d0746458502554c | mm: try_to_unmap_cluster() should lock_page() before mlocking
A BUG_ON(!PageLocked) was triggered in mlock_vma_page() by Sasha Levin
fuzzing with trinity. The call site try_to_unmap_cluster() does not lock
the pages other than its check_page parameter (which is already locked).
The BUG_ON in mlock_vma_page() is not ... | 0 | vma_address(struct page *page, struct vm_area_struct *vma)
{
unsigned long address = __vma_address(page, vma);
/* page should be within @vma mapping range */
VM_BUG_ON(address < vma->vm_start || address >= vma->vm_end);
return address;
}
| 301,515,869,526,986,540,000,000,000,000,000,000,000 | rmap.c | 167,349,147,755,281,770,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-3122 | The try_to_unmap_cluster function in mm/rmap.c in the Linux kernel before 3.14.3 does not properly consider which pages must be locked, which allows local users to cause a denial of service (system crash) by triggering a memory-usage pattern that requires removal of page-table mappings. | https://nvd.nist.gov/vuln/detail/CVE-2014-3122 |
38,843 | linux | a03ffcf873fe0f2565386ca8ef832144c42e67fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a03ffcf873fe0f2565386ca8ef832144c42e67fa | net: bpf_jit: fix an off-one bug in x86_64 cond jump target
x86 jump instruction size is 2 or 5 bytes (near/long jump), not 2 or 6
bytes.
In case a conditional jump is followed by a long jump, conditional jump
target is one byte past the start of target instruction.
Signed-off-by: Markus Kötter <nepenthesdev@gmail.c... | 0 | static inline void bpf_flush_icache(void *start, void *end)
{
mm_segment_t old_fs = get_fs();
set_fs(KERNEL_DS);
smp_wmb();
flush_icache_range((unsigned long)start, (unsigned long)end);
set_fs(old_fs);
}
| 302,608,321,201,763,060,000,000,000,000,000,000,000 | bpf_jit_comp.c | 114,327,817,519,201,570,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-2889 | Off-by-one error in the bpf_jit_compile function in arch/x86/net/bpf_jit_comp.c in the Linux kernel before 3.1.8, when BPF JIT is enabled, allows local users to cause a denial of service (system crash) or possibly gain privileges via a long jump after a conditional jump. | https://nvd.nist.gov/vuln/detail/CVE-2014-2889 |
38,844 | linux | a03ffcf873fe0f2565386ca8ef832144c42e67fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a03ffcf873fe0f2565386ca8ef832144c42e67fa | net: bpf_jit: fix an off-one bug in x86_64 cond jump target
x86 jump instruction size is 2 or 5 bytes (near/long jump), not 2 or 6
bytes.
In case a conditional jump is followed by a long jump, conditional jump
target is one byte past the start of target instruction.
Signed-off-by: Markus Kötter <nepenthesdev@gmail.c... | 0 | void bpf_jit_free(struct sk_filter *fp)
{
if (fp->bpf_func != sk_run_filter) {
struct work_struct *work = (struct work_struct *)fp->bpf_func;
INIT_WORK(work, jit_free_defer);
schedule_work(work);
}
}
| 41,920,996,570,949,125,000,000,000,000,000,000,000 | bpf_jit_comp.c | 114,327,817,519,201,570,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-2889 | Off-by-one error in the bpf_jit_compile function in arch/x86/net/bpf_jit_comp.c in the Linux kernel before 3.1.8, when BPF JIT is enabled, allows local users to cause a denial of service (system crash) or possibly gain privileges via a long jump after a conditional jump. | https://nvd.nist.gov/vuln/detail/CVE-2014-2889 |
38,845 | linux | a03ffcf873fe0f2565386ca8ef832144c42e67fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a03ffcf873fe0f2565386ca8ef832144c42e67fa | net: bpf_jit: fix an off-one bug in x86_64 cond jump target
x86 jump instruction size is 2 or 5 bytes (near/long jump), not 2 or 6
bytes.
In case a conditional jump is followed by a long jump, conditional jump
target is one byte past the start of target instruction.
Signed-off-by: Markus Kötter <nepenthesdev@gmail.c... | 0 | static inline u8 *emit_code(u8 *ptr, u32 bytes, unsigned int len)
{
if (len == 1)
*ptr = bytes;
else if (len == 2)
*(u16 *)ptr = bytes;
else {
*(u32 *)ptr = bytes;
barrier();
}
return ptr + len;
}
| 251,981,264,367,156,300,000,000,000,000,000,000,000 | bpf_jit_comp.c | 114,327,817,519,201,570,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-2889 | Off-by-one error in the bpf_jit_compile function in arch/x86/net/bpf_jit_comp.c in the Linux kernel before 3.1.8, when BPF JIT is enabled, allows local users to cause a denial of service (system crash) or possibly gain privileges via a long jump after a conditional jump. | https://nvd.nist.gov/vuln/detail/CVE-2014-2889 |
38,846 | linux | a03ffcf873fe0f2565386ca8ef832144c42e67fa | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/a03ffcf873fe0f2565386ca8ef832144c42e67fa | net: bpf_jit: fix an off-one bug in x86_64 cond jump target
x86 jump instruction size is 2 or 5 bytes (near/long jump), not 2 or 6
bytes.
In case a conditional jump is followed by a long jump, conditional jump
target is one byte past the start of target instruction.
Signed-off-by: Markus Kötter <nepenthesdev@gmail.c... | 0 | static inline bool is_near(int offset)
{
return offset <= 127 && offset >= -128;
}
| 19,080,371,856,644,992,000,000,000,000,000,000,000 | bpf_jit_comp.c | 114,327,817,519,201,570,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2014-2889 | Off-by-one error in the bpf_jit_compile function in arch/x86/net/bpf_jit_comp.c in the Linux kernel before 3.1.8, when BPF JIT is enabled, allows local users to cause a denial of service (system crash) or possibly gain privileges via a long jump after a conditional jump. | https://nvd.nist.gov/vuln/detail/CVE-2014-2889 |
38,847 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int be32_gt(__be32 a, __be32 b)
{
return (__force u32) a > (__force u32) b;
}
| 316,389,514,225,838,800,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,848 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int be32_lt(__be32 a, __be32 b)
{
return (__force u32) a < (__force u32) b;
}
| 185,903,199,206,316,950,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,849 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int be64_lt(__be64 a, __be64 b)
{
return (__force u64) a < (__force u64) b;
}
| 310,720,942,969,797,000,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,850 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static u8 cm_ack_timeout(u8 ca_ack_delay, u8 packet_life_time)
{
int ack_timeout = packet_life_time + 1;
if (ack_timeout >= ca_ack_delay)
ack_timeout += (ca_ack_delay >= (ack_timeout - 1));
else
ack_timeout = ca_ack_delay +
(ack_timeout >= (ca_ack_delay - 1));
return min(31, ack_timeout);
}
| 154,785,549,986,425,750,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,851 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static struct cm_id_private * cm_acquire_mraed_id(struct cm_mra_msg *mra_msg)
{
switch (cm_mra_get_msg_mraed(mra_msg)) {
case CM_MSG_RESPONSE_REQ:
return cm_acquire_id(mra_msg->remote_comm_id, 0);
case CM_MSG_RESPONSE_REP:
case CM_MSG_RESPONSE_OTHER:
return cm_acquire_id(mra_msg->remote_comm_id,
mra_ms... | 57,442,521,588,111,940,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,852 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static struct cm_id_private * cm_acquire_rejected_id(struct cm_rej_msg *rej_msg)
{
struct cm_timewait_info *timewait_info;
struct cm_id_private *cm_id_priv;
__be32 remote_id;
remote_id = rej_msg->local_comm_id;
if (__be16_to_cpu(rej_msg->reason) == IB_CM_REJ_TIMEOUT) {
spin_lock_irq(&cm.lock);
timewait_info ... | 40,732,197,401,684,720,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,853 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_alloc_id(struct cm_id_private *cm_id_priv)
{
unsigned long flags;
int id;
idr_preload(GFP_KERNEL);
spin_lock_irqsave(&cm.lock, flags);
id = idr_alloc_cyclic(&cm.local_id_table, cm_id_priv, 0, 0, GFP_NOWAIT);
spin_unlock_irqrestore(&cm.lock, flags);
idr_preload_end();
cm_id_priv->id.local_id = ... | 9,109,245,646,050,428,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,854 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_alloc_msg(struct cm_id_private *cm_id_priv,
struct ib_mad_send_buf **msg)
{
struct ib_mad_agent *mad_agent;
struct ib_mad_send_buf *m;
struct ib_ah *ah;
mad_agent = cm_id_priv->av.port->mad_agent;
ah = ib_create_ah(mad_agent->qp->pd, &cm_id_priv->av.ah_attr);
if (IS_ERR(ah))
return PTR_ERR(ah)... | 80,946,610,440,624,860,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,855 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_alloc_response_msg(struct cm_port *port,
struct ib_mad_recv_wc *mad_recv_wc,
struct ib_mad_send_buf **msg)
{
struct ib_mad_send_buf *m;
struct ib_ah *ah;
ah = ib_create_ah_from_wc(port->mad_agent->qp->pd, mad_recv_wc->wc,
mad_recv_wc->recv_buf.grh, port->port_num);
if (IS_ERR(ah))
r... | 204,348,569,028,550,840,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,856 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_apr_handler(struct cm_work *work)
{
struct cm_id_private *cm_id_priv;
struct cm_apr_msg *apr_msg;
int ret;
apr_msg = (struct cm_apr_msg *)work->mad_recv_wc->recv_buf.mad;
cm_id_priv = cm_acquire_id(apr_msg->remote_comm_id,
apr_msg->local_comm_id);
if (!cm_id_priv)
return -EINVAL; /* Unmatc... | 322,373,947,481,708,500,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,857 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_compare_data(struct ib_cm_compare_data *src_data,
struct ib_cm_compare_data *dst_data)
{
u8 src[IB_CM_COMPARE_SIZE];
u8 dst[IB_CM_COMPARE_SIZE];
if (!src_data || !dst_data)
return 0;
cm_mask_copy(src, src_data->data, dst_data->mask);
cm_mask_copy(dst, dst_data->data, src_data->mask);
retur... | 79,691,664,363,181,490,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,858 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static inline int cm_convert_to_ms(int iba_time)
{
/* approximate conversion to ms from 4.096us x 2^iba_time */
return 1 << max(iba_time - 8, 0);
}
| 98,377,494,597,417,260,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,859 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_create_port_fs(struct cm_port *port)
{
int i, ret;
ret = kobject_init_and_add(&port->port_obj, &cm_port_obj_type,
&port->cm_dev->device->kobj,
"%d", port->port_num);
if (ret) {
kfree(port);
return ret;
}
for (i = 0; i < CM_COUNTER_GROUPS; i++) {
ret = kobject_init_and_add(&port-... | 180,364,565,679,388,470,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,860 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static struct cm_timewait_info * cm_create_timewait_info(__be32 local_id)
{
struct cm_timewait_info *timewait_info;
timewait_info = kzalloc(sizeof *timewait_info, GFP_KERNEL);
if (!timewait_info)
return ERR_PTR(-ENOMEM);
timewait_info->work.local_id = local_id;
INIT_DELAYED_WORK(&timewait_info->work.work, cm_w... | 291,318,439,833,138,430,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,861 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static struct cm_work * cm_dequeue_work(struct cm_id_private *cm_id_priv)
{
struct cm_work *work;
if (list_empty(&cm_id_priv->work_list))
return NULL;
work = list_entry(cm_id_priv->work_list.next, struct cm_work, list);
list_del(&work->list);
return work;
}
| 186,917,782,907,506,830,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,862 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static inline void cm_deref_id(struct cm_id_private *cm_id_priv)
{
if (atomic_dec_and_test(&cm_id_priv->refcount))
complete(&cm_id_priv->comp);
}
| 11,766,070,880,126,612,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,863 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_destroy_id(struct ib_cm_id *cm_id, int err)
{
struct cm_id_private *cm_id_priv;
struct cm_work *work;
cm_id_priv = container_of(cm_id, struct cm_id_private, id);
retest:
spin_lock_irq(&cm_id_priv->lock);
switch (cm_id->state) {
case IB_CM_LISTEN:
cm_id->state = IB_CM_IDLE;
spin_unlock_irq(&cm_... | 318,369,010,193,223,500,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,864 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static char *cm_devnode(struct device *dev, umode_t *mode)
{
if (mode)
*mode = 0666;
return kasprintf(GFP_KERNEL, "infiniband/%s", dev_name(dev));
}
| 54,005,219,269,425,870,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,865 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_drep_handler(struct cm_work *work)
{
struct cm_id_private *cm_id_priv;
struct cm_drep_msg *drep_msg;
int ret;
drep_msg = (struct cm_drep_msg *)work->mad_recv_wc->recv_buf.mad;
cm_id_priv = cm_acquire_id(drep_msg->remote_comm_id,
drep_msg->local_comm_id);
if (!cm_id_priv)
return -EINVAL;
... | 156,385,224,591,200,970,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,866 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_dreq_handler(struct cm_work *work)
{
struct cm_id_private *cm_id_priv;
struct cm_dreq_msg *dreq_msg;
struct ib_mad_send_buf *msg = NULL;
int ret;
dreq_msg = (struct cm_dreq_msg *)work->mad_recv_wc->recv_buf.mad;
cm_id_priv = cm_acquire_id(dreq_msg->remote_comm_id,
dreq_msg->local_comm_id);
... | 291,858,766,502,205,070,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,867 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_dup_rep_handler(struct cm_work *work)
{
struct cm_id_private *cm_id_priv;
struct cm_rep_msg *rep_msg;
struct ib_mad_send_buf *msg = NULL;
int ret;
rep_msg = (struct cm_rep_msg *) work->mad_recv_wc->recv_buf.mad;
cm_id_priv = cm_acquire_id(rep_msg->remote_comm_id,
rep_msg->local_comm_id);
i... | 26,557,626,979,053,076,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,868 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_dup_req_handler(struct cm_work *work,
struct cm_id_private *cm_id_priv)
{
struct ib_mad_send_buf *msg = NULL;
int ret;
atomic_long_inc(&work->port->counter_group[CM_RECV_DUPLICATES].
counter[CM_REQ_COUNTER]);
/* Quick state check to discard duplicate REQs. */
if (cm_id_priv->id.state ... | 55,808,263,487,933,690,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,869 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_enter_timewait(struct cm_id_private *cm_id_priv)
{
int wait_time;
unsigned long flags;
spin_lock_irqsave(&cm.lock, flags);
cm_cleanup_timewait(cm_id_priv->timewait_info);
list_add_tail(&cm_id_priv->timewait_info->list, &cm.timewait_list);
spin_unlock_irqrestore(&cm.lock, flags);
/*
* The cm_id... | 200,756,712,839,094,920,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,870 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_establish(struct ib_cm_id *cm_id)
{
struct cm_id_private *cm_id_priv;
struct cm_work *work;
unsigned long flags;
int ret = 0;
work = kmalloc(sizeof *work, GFP_ATOMIC);
if (!work)
return -ENOMEM;
cm_id_priv = container_of(cm_id, struct cm_id_private, id);
spin_lock_irqsave(&cm_id_priv->lock, fl... | 104,068,533,663,039,080,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,871 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static int cm_establish_handler(struct cm_work *work)
{
struct cm_id_private *cm_id_priv;
int ret;
/* See comment in cm_establish about lookup. */
cm_id_priv = cm_acquire_id(work->local_id, work->remote_id);
if (!cm_id_priv)
return -EINVAL;
spin_lock_irq(&cm_id_priv->lock);
if (cm_id_priv->id.state != IB_CM_... | 70,747,997,197,731,150,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,872 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static struct cm_id_private * cm_find_listen(struct ib_device *device,
__be64 service_id,
u8 *private_data)
{
struct rb_node *node = cm.listen_service_table.rb_node;
struct cm_id_private *cm_id_priv;
int data_cmp;
while (node) {
cm_id_priv = rb_entry(node, struct cm_id_private, service_node);... | 166,045,997,983,981,270,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,873 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_drep(struct cm_drep_msg *drep_msg,
struct cm_id_private *cm_id_priv,
const void *private_data,
u8 private_data_len)
{
cm_format_mad_hdr(&drep_msg->hdr, CM_DREP_ATTR_ID, cm_id_priv->tid);
drep_msg->local_comm_id = cm_id_priv->id.local_id;
drep_msg->remote_comm_id = cm_id_priv->id.... | 160,228,478,547,876,390,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,874 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_dreq(struct cm_dreq_msg *dreq_msg,
struct cm_id_private *cm_id_priv,
const void *private_data,
u8 private_data_len)
{
cm_format_mad_hdr(&dreq_msg->hdr, CM_DREQ_ATTR_ID,
cm_form_tid(cm_id_priv, CM_MSG_SEQUENCE_DREQ));
dreq_msg->local_comm_id = cm_id_priv->id.local_id;
dreq_ms... | 53,639,547,090,555,500,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,875 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_lap(struct cm_lap_msg *lap_msg,
struct cm_id_private *cm_id_priv,
struct ib_sa_path_rec *alternate_path,
const void *private_data,
u8 private_data_len)
{
cm_format_mad_hdr(&lap_msg->hdr, CM_LAP_ATTR_ID,
cm_form_tid(cm_id_priv, CM_MSG_SEQUENCE_LAP));
lap_msg->local_comm_i... | 282,672,974,679,254,200,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,876 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_mad_hdr(struct ib_mad_hdr *hdr,
__be16 attr_id, __be64 tid)
{
hdr->base_version = IB_MGMT_BASE_VERSION;
hdr->mgmt_class = IB_MGMT_CLASS_CM;
hdr->class_version = IB_CM_CLASS_VERSION;
hdr->method = IB_MGMT_METHOD_SEND;
hdr->attr_id = attr_id;
hdr->tid = tid;
}
| 78,753,166,678,756,460,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,877 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_mra(struct cm_mra_msg *mra_msg,
struct cm_id_private *cm_id_priv,
enum cm_msg_response msg_mraed, u8 service_timeout,
const void *private_data, u8 private_data_len)
{
cm_format_mad_hdr(&mra_msg->hdr, CM_MRA_ATTR_ID, cm_id_priv->tid);
cm_mra_set_msg_mraed(mra_msg, msg_mraed);
mra_... | 190,279,683,794,843,960,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,878 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_path_from_lap(struct cm_id_private *cm_id_priv,
struct ib_sa_path_rec *path,
struct cm_lap_msg *lap_msg)
{
memset(path, 0, sizeof *path);
path->dgid = lap_msg->alt_local_gid;
path->sgid = lap_msg->alt_remote_gid;
path->dlid = lap_msg->alt_local_lid;
path->slid = lap_msg->alt_r... | 245,480,587,031,244,930,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,879 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_rej(struct cm_rej_msg *rej_msg,
struct cm_id_private *cm_id_priv,
enum ib_cm_rej_reason reason,
void *ari,
u8 ari_length,
const void *private_data,
u8 private_data_len)
{
cm_format_mad_hdr(&rej_msg->hdr, CM_REJ_ATTR_ID, cm_id_priv->tid);
rej_msg->remote_comm_id = cm... | 273,149,259,319,331,160,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,880 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_rej_event(struct cm_work *work)
{
struct cm_rej_msg *rej_msg;
struct ib_cm_rej_event_param *param;
rej_msg = (struct cm_rej_msg *)work->mad_recv_wc->recv_buf.mad;
param = &work->cm_event.param.rej_rcvd;
param->ari = rej_msg->ari;
param->ari_length = cm_rej_get_reject_info_len(rej_msg);
par... | 153,174,838,260,430,400,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,881 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_rep(struct cm_rep_msg *rep_msg,
struct cm_id_private *cm_id_priv,
struct ib_cm_rep_param *param)
{
cm_format_mad_hdr(&rep_msg->hdr, CM_REP_ATTR_ID, cm_id_priv->tid);
rep_msg->local_comm_id = cm_id_priv->id.local_id;
rep_msg->remote_comm_id = cm_id_priv->id.remote_id;
cm_rep_set_start... | 190,361,380,142,730,860,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
38,882 | linux | b2853fd6c2d0f383dbdf7427e263eb576a633867 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/b2853fd6c2d0f383dbdf7427e263eb576a633867 | IB/core: Don't resolve passive side RoCE L2 address in CMA REQ handler
The code that resolves the passive side source MAC within the rdma_cm
connection request handler was both redundant and buggy, so remove it.
It was redundant since later, when an RC QP is modified to RTR state,
the resolution will take place in th... | 0 | static void cm_format_rep_event(struct cm_work *work, enum ib_qp_type qp_type)
{
struct cm_rep_msg *rep_msg;
struct ib_cm_rep_event_param *param;
rep_msg = (struct cm_rep_msg *)work->mad_recv_wc->recv_buf.mad;
param = &work->cm_event.param.rep_rcvd;
param->remote_ca_guid = rep_msg->local_ca_guid;
param->remote_q... | 297,009,022,755,813,640,000,000,000,000,000,000,000 | cm.c | 28,129,333,480,100,836,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-2739 | The cma_req_handler function in drivers/infiniband/core/cma.c in the Linux kernel 3.14.x through 3.14.1 attempts to resolve an RDMA over Converged Ethernet (aka RoCE) address that is properly resolved within a different module, which allows remote attackers to cause a denial of service (incorrect pointer dereference an... | https://nvd.nist.gov/vuln/detail/CVE-2014-2739 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.