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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
39,302 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int compute_sid_handle_invalid_context(
struct context *scontext,
struct context *tcontext,
u16 tclass,
struct context *newcontext)
{
char *s = NULL, *t = NULL, *n = NULL;
u32 slen, tlen, nlen;
if (context_struct_to_string(scontext, &s, &slen))
goto out;
if (context_struct_to_string(tcontext, &t, &tle... | 223,207,863,133,044,440,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,303 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int constraint_expr_eval(struct context *scontext,
struct context *tcontext,
struct context *xcontext,
struct constraint_expr *cexpr)
{
u32 val1, val2;
struct context *c;
struct role_datum *r1, *r2;
struct mls_level *l1, *l2;
struct constraint_expr *e;
int s[CEXPR_MAXDEPTH];
int sp = -1;
for... | 38,051,343,082,253,010,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,304 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int context_struct_to_string(struct context *context, char **scontext, u32 *scontext_len)
{
char *scontextp;
if (scontext)
*scontext = NULL;
*scontext_len = 0;
if (context->len) {
*scontext_len = context->len;
if (scontext) {
*scontext = kstrdup(context->str, GFP_ATOMIC);
if (!(*scontext))
... | 186,408,978,098,096,570,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,305 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int convert_context(u32 key,
struct context *c,
void *p)
{
struct convert_context_args *args;
struct context oldc;
struct ocontext *oc;
struct mls_range *range;
struct role_datum *role;
struct type_datum *typdatum;
struct user_datum *usrdatum;
char *s;
u32 len;
int rc = 0;
if (key <= SECI... | 40,313,443,091,012,270,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,306 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static inline int convert_context_handle_invalid_context(struct context *context)
{
char *s;
u32 len;
if (selinux_enforcing)
return -EINVAL;
if (!context_struct_to_string(context, &s, &len)) {
printk(KERN_WARNING "SELinux: Context %s would be invalid if enforcing\n", s);
kfree(s);
}
return 0;
}
| 168,261,421,328,441,060,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,307 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int dump_masked_av_helper(void *k, void *d, void *args)
{
struct perm_datum *pdatum = d;
char **permission_names = args;
BUG_ON(pdatum->value < 1 || pdatum->value > 32);
permission_names[pdatum->value - 1] = (char *)k;
return 0;
}
| 209,946,714,840,082,600,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,308 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static void filename_compute_type(struct policydb *p, struct context *newcontext,
u32 stype, u32 ttype, u16 tclass,
const char *objname)
{
struct filename_trans ft;
struct filename_trans_datum *otype;
/*
* Most filename trans rules are going to live in specific directories
* like /dev or /var/run. ... | 260,668,267,155,483,030,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,309 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int get_classes_callback(void *k, void *d, void *args)
{
struct class_datum *datum = d;
char *name = k, **classes = args;
int value = datum->value - 1;
classes[value] = kstrdup(name, GFP_ATOMIC);
if (!classes[value])
return -ENOMEM;
return 0;
}
| 247,483,270,160,085,250,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,310 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int get_permissions_callback(void *k, void *d, void *args)
{
struct perm_datum *datum = d;
char *name = k, **perms = args;
int value = datum->value - 1;
perms[value] = kstrdup(name, GFP_ATOMIC);
if (!perms[value])
return -ENOMEM;
return 0;
}
| 44,449,889,486,387,770,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,311 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static u16 map_class(u16 pol_value)
{
u16 i;
for (i = 1; i < current_mapping_size; i++) {
if (current_mapping[i].value == pol_value)
return i;
}
return SECCLASS_NULL;
}
| 311,430,626,333,613,180,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,312 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static void map_decision(u16 tclass, struct av_decision *avd,
int allow_unknown)
{
if (tclass < current_mapping_size) {
unsigned i, n = current_mapping[tclass].num_perms;
u32 result;
for (i = 0, result = 0; i < n; i++) {
if (avd->allowed & current_mapping[tclass].perms[i])
result |= 1<<i;
if (allo... | 306,240,915,851,036,640,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,313 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int match_ipv6_addrmask(u32 *input, u32 *addr, u32 *mask)
{
int i, fail = 0;
for (i = 0; i < 4; i++)
if (addr[i] != (input[i] & mask[i])) {
fail = 1;
break;
}
return !fail;
}
| 230,239,487,470,525,930,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,314 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_bounded_transition(u32 old_sid, u32 new_sid)
{
struct context *old_context, *new_context;
struct type_datum *type;
int index;
int rc;
read_lock(&policy_rwlock);
rc = -EINVAL;
old_context = sidtab_search(&sidtab, old_sid);
if (!old_context) {
printk(KERN_ERR "SELinux: %s: unrecognized SID %u\n",... | 294,137,373,494,502,200,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,315 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_change_sid(u32 ssid,
u32 tsid,
u16 tclass,
u32 *out_sid)
{
return security_compute_sid(ssid, tsid, tclass, AVTAB_CHANGE, NULL,
out_sid, false);
}
| 317,869,366,602,408,360,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,316 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | void security_compute_av(u32 ssid,
u32 tsid,
u16 orig_tclass,
struct av_decision *avd)
{
u16 tclass;
struct context *scontext = NULL, *tcontext = NULL;
read_lock(&policy_rwlock);
avd_init(avd);
if (!ss_initialized)
goto allow;
scontext = sidtab_search(&sidtab, ssid);
if (!scontext) {
printk(KER... | 84,222,640,321,135,940,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,317 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | void security_compute_av_user(u32 ssid,
u32 tsid,
u16 tclass,
struct av_decision *avd)
{
struct context *scontext = NULL, *tcontext = NULL;
read_lock(&policy_rwlock);
avd_init(avd);
if (!ss_initialized)
goto allow;
scontext = sidtab_search(&sidtab, ssid);
if (!scontext) {
printk(K... | 40,421,769,989,151,180,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,318 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int security_compute_sid(u32 ssid,
u32 tsid,
u16 orig_tclass,
u32 specified,
const char *objname,
u32 *out_sid,
bool kern)
{
struct class_datum *cladatum = NULL;
struct context *scontext = NULL, *tcontext = NULL, newcontext;
struct role_trans *roletr = NULL;
struct avtab_key avkey;
s... | 291,744,386,088,608,400,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,319 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_context_to_sid(const char *scontext, u32 scontext_len, u32 *sid)
{
return security_context_to_sid_core(scontext, scontext_len,
sid, SECSID_NULL, GFP_KERNEL, 0);
}
| 72,369,821,817,891,150,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,320 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_context_to_sid_default(const char *scontext, u32 scontext_len,
u32 *sid, u32 def_sid, gfp_t gfp_flags)
{
return security_context_to_sid_core(scontext, scontext_len,
sid, def_sid, gfp_flags, 1);
}
| 59,299,037,488,682,120,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,321 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_context_to_sid_force(const char *scontext, u32 scontext_len,
u32 *sid)
{
return security_context_to_sid_core(scontext, scontext_len,
sid, SECSID_NULL, GFP_KERNEL, 1);
}
| 305,449,477,757,335,730,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,322 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static void security_dump_masked_av(struct context *scontext,
struct context *tcontext,
u16 tclass,
u32 permissions,
const char *reason)
{
struct common_datum *common_dat;
struct class_datum *tclass_dat;
struct audit_buffer *ab;
char *tclass_name;
char *scontext_name = NULL;
char *... | 156,076,235,370,522,200,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,323 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_fs_use(struct super_block *sb)
{
int rc = 0;
struct ocontext *c;
struct superblock_security_struct *sbsec = sb->s_security;
const char *fstype = sb->s_type->name;
read_lock(&policy_rwlock);
c = policydb.ocontexts[OCON_FSUSE];
while (c) {
if (strcmp(fstype, c->u.name) == 0)
break;
c = c->nex... | 304,894,893,968,552,430,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,324 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_get_allow_unknown(void)
{
return policydb.allow_unknown;
}
| 251,617,459,859,478,800,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,325 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_get_bool_value(int bool)
{
int rc;
int len;
read_lock(&policy_rwlock);
rc = -EFAULT;
len = policydb.p_bools.nprim;
if (bool >= len)
goto out;
rc = policydb.bool_val_to_struct[bool]->state;
out:
read_unlock(&policy_rwlock);
return rc;
}
| 97,383,688,047,831,970,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,326 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_get_classes(char ***classes, int *nclasses)
{
int rc;
read_lock(&policy_rwlock);
rc = -ENOMEM;
*nclasses = policydb.p_classes.nprim;
*classes = kcalloc(*nclasses, sizeof(**classes), GFP_ATOMIC);
if (!*classes)
goto out;
rc = hashtab_map(policydb.p_classes.table, get_classes_callback,
*classe... | 149,426,981,425,013,360,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,327 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | const char *security_get_initial_sid_context(u32 sid)
{
if (unlikely(sid > SECINITSID_NUM))
return NULL;
return initial_sid_to_string[sid];
}
| 95,787,532,366,828,870,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,328 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_get_permissions(char *class, char ***perms, int *nperms)
{
int rc, i;
struct class_datum *match;
read_lock(&policy_rwlock);
rc = -EINVAL;
match = hashtab_search(policydb.p_classes.table, class);
if (!match) {
printk(KERN_ERR "SELinux: %s: unrecognized class %s\n",
__func__, class);
goto out... | 151,821,757,850,757,700,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,329 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_get_reject_unknown(void)
{
return policydb.reject_unknown;
}
| 124,275,419,821,946,640,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,330 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_get_user_sids(u32 fromsid,
char *username,
u32 **sids,
u32 *nel)
{
struct context *fromcon, usercon;
u32 *mysids = NULL, *mysids2, sid;
u32 mynel = 0, maxnel = SIDS_NEL;
struct user_datum *user;
struct role_datum *role;
struct ebitmap_node *rnode, *tnode;
int rc = 0, i, j;
*sids ... | 298,055,844,823,084,520,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,331 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_load_policy(void *data, size_t len)
{
struct policydb *oldpolicydb, *newpolicydb;
struct sidtab oldsidtab, newsidtab;
struct selinux_mapping *oldmap, *map = NULL;
struct convert_context_args args;
u32 seqno;
u16 map_size;
int rc = 0;
struct policy_file file = { data, len }, *fp = &file;
oldpolicy... | 251,460,674,753,232,170,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,332 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_member_sid(u32 ssid,
u32 tsid,
u16 tclass,
u32 *out_sid)
{
return security_compute_sid(ssid, tsid, tclass, AVTAB_MEMBER, NULL,
out_sid, false);
}
| 233,568,431,572,929,870,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,333 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_mls_enabled(void)
{
return policydb.mls_enabled;
}
| 67,146,933,857,049,530,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,334 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_net_peersid_resolve(u32 nlbl_sid, u32 nlbl_type,
u32 xfrm_sid,
u32 *peer_sid)
{
int rc;
struct context *nlbl_ctx;
struct context *xfrm_ctx;
*peer_sid = SECSID_NULL;
/* handle the common (which also happens to be the set of easy) cases
* right away, these two if statements catch everythin... | 100,842,983,172,191,520,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,335 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_netif_sid(char *name, u32 *if_sid)
{
int rc = 0;
struct ocontext *c;
read_lock(&policy_rwlock);
c = policydb.ocontexts[OCON_NETIF];
while (c) {
if (strcmp(name, c->u.name) == 0)
break;
c = c->next;
}
if (c) {
if (!c->sid[0] || !c->sid[1]) {
rc = sidtab_context_to_sid(&sidtab,
... | 238,823,143,849,800,260,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,336 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static void security_netlbl_cache_add(struct netlbl_lsm_secattr *secattr,
u32 sid)
{
u32 *sid_cache;
sid_cache = kmalloc(sizeof(*sid_cache), GFP_ATOMIC);
if (sid_cache == NULL)
return;
secattr->cache = netlbl_secattr_cache_alloc(GFP_ATOMIC);
if (secattr->cache == NULL) {
kfree(sid_cache);
return;
... | 188,768,237,325,353,850,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,337 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_netlbl_sid_to_secattr(u32 sid, struct netlbl_lsm_secattr *secattr)
{
int rc;
struct context *ctx;
if (!ss_initialized)
return 0;
read_lock(&policy_rwlock);
rc = -ENOENT;
ctx = sidtab_search(&sidtab, sid);
if (ctx == NULL)
goto out;
rc = -ENOMEM;
secattr->domain = kstrdup(sym_name(&policydb... | 68,472,517,567,000,120,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,338 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_node_sid(u16 domain,
void *addrp,
u32 addrlen,
u32 *out_sid)
{
int rc;
struct ocontext *c;
read_lock(&policy_rwlock);
switch (domain) {
case AF_INET: {
u32 addr;
rc = -EINVAL;
if (addrlen != sizeof(u32))
goto out;
addr = *((u32 *)addrp);
c = policydb.ocontexts... | 263,533,207,367,562,980,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,339 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_policycap_supported(unsigned int req_cap)
{
int rc;
read_lock(&policy_rwlock);
rc = ebitmap_get_bit(&policydb.policycaps, req_cap);
read_unlock(&policy_rwlock);
return rc;
}
| 197,617,732,737,991,200,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,340 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | size_t security_policydb_len(void)
{
size_t len;
read_lock(&policy_rwlock);
len = policydb.len;
read_unlock(&policy_rwlock);
return len;
}
| 324,179,454,469,242,300,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,341 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_port_sid(u8 protocol, u16 port, u32 *out_sid)
{
struct ocontext *c;
int rc = 0;
read_lock(&policy_rwlock);
c = policydb.ocontexts[OCON_PORT];
while (c) {
if (c->u.port.protocol == protocol &&
c->u.port.low_port <= port &&
c->u.port.high_port >= port)
break;
c = c->next;
}
if (c... | 145,554,314,542,848,460,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,342 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int security_preserve_bools(struct policydb *p)
{
int rc, nbools = 0, *bvalues = NULL, i;
char **bnames = NULL;
struct cond_bool_datum *booldatum;
struct cond_node *cur;
rc = security_get_bools(&nbools, &bnames, &bvalues);
if (rc)
goto out;
for (i = 0; i < nbools; i++) {
booldatum = hashtab_search(p-... | 105,983,195,531,210,780,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,343 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_set_bools(int len, int *values)
{
int i, rc;
int lenp, seqno = 0;
struct cond_node *cur;
write_lock_irq(&policy_rwlock);
rc = -EFAULT;
lenp = policydb.p_bools.nprim;
if (len != lenp)
goto out;
for (i = 0; i < len; i++) {
if (!!values[i] != policydb.bool_val_to_struct[i]->state) {
audit_lo... | 333,262,083,528,910,360,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,344 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_sid_to_context(u32 sid, char **scontext, u32 *scontext_len)
{
return security_sid_to_context_core(sid, scontext, scontext_len, 0);
}
| 305,170,955,644,300,220,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,345 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int security_sid_to_context_core(u32 sid, char **scontext,
u32 *scontext_len, int force)
{
struct context *context;
int rc = 0;
if (scontext)
*scontext = NULL;
*scontext_len = 0;
if (!ss_initialized) {
if (sid <= SECINITSID_NUM) {
char *scontextp;
*scontext_len = strlen(initial_sid_to_str... | 241,335,407,861,073,440,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,346 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_transition_sid(u32 ssid, u32 tsid, u16 tclass,
const struct qstr *qstr, u32 *out_sid)
{
return security_compute_sid(ssid, tsid, tclass, AVTAB_TRANSITION,
qstr ? qstr->name : NULL, out_sid, true);
}
| 132,197,163,161,726,480,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,347 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_transition_sid_user(u32 ssid, u32 tsid, u16 tclass,
const char *objname, u32 *out_sid)
{
return security_compute_sid(ssid, tsid, tclass, AVTAB_TRANSITION,
objname, out_sid, false);
}
| 237,132,085,585,192,400,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,348 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int security_validate_transition(u32 oldsid, u32 newsid, u32 tasksid,
u16 orig_tclass)
{
struct context *ocontext;
struct context *ncontext;
struct context *tcontext;
struct class_datum *tclass_datum;
struct constraint_node *constraint;
u16 tclass;
int rc = 0;
if (!ss_initialized)
return 0;
read_lock(... | 271,054,126,614,900,340,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,349 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int security_validtrans_handle_fail(struct context *ocontext,
struct context *ncontext,
struct context *tcontext,
u16 tclass)
{
char *o = NULL, *n = NULL, *t = NULL;
u32 olen, nlen, tlen;
if (context_struct_to_string(ocontext, &o, &olen))
goto out;
if (context_struct_to_string(ncon... | 236,266,120,721,618,600,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,350 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | void selinux_audit_rule_free(void *vrule)
{
struct selinux_audit_rule *rule = vrule;
if (rule) {
context_destroy(&rule->au_ctxt);
kfree(rule);
}
}
| 4,037,353,070,563,879,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,351 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | int selinux_audit_rule_match(u32 sid, u32 field, u32 op, void *vrule,
struct audit_context *actx)
{
struct context *ctxt;
struct mls_level *level;
struct selinux_audit_rule *rule = vrule;
int match = 0;
if (!rule) {
audit_log(actx, GFP_ATOMIC, AUDIT_SELINUX_ERR,
"selinux_audit_rule_match: missing r... | 280,169,041,250,726,600,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,352 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int selinux_set_mapping(struct policydb *pol,
struct security_class_mapping *map,
struct selinux_mapping **out_map_p,
u16 *out_map_size)
{
struct selinux_mapping *out_map = NULL;
size_t size = sizeof(struct selinux_mapping);
u16 i, j;
unsigned k;
bool print_unknown_handle = fal... | 235,613,762,006,032,550,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,353 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static int string_to_context_struct(struct policydb *pol,
struct sidtab *sidtabp,
char *scontext,
u32 scontext_len,
struct context *ctx,
u32 def_sid)
{
struct role_datum *role;
struct type_datum *typdatum;
struct user_datum *usrdatum;
char *scontextp, *p, oldc;
int rc = 0;
... | 222,021,378,200,703,900,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,354 | linux | 2172fa709ab32ca60e86179dc67d0857be8e2c98 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2172fa709ab32ca60e86179dc67d0857be8e2c98 | SELinux: Fix kernel BUG on empty security contexts.
Setting an empty security context (length=0) on a file will
lead to incorrectly dereferencing the type and other fields
of the security context structure, yielding a kernel BUG.
As a zero-length security context is never valid, just reject
all such security contexts... | 0 | static void type_attribute_bounds_av(struct context *scontext,
struct context *tcontext,
u16 tclass,
struct av_decision *avd)
{
struct context lo_scontext;
struct context lo_tcontext;
struct av_decision lo_avd;
struct type_datum *source;
struct type_datum *target;
u32 masked = 0;
sour... | 23,782,219,956,593,615,000,000,000,000,000,000,000 | services.c | 185,065,927,068,298,400,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2014-1874 | The security_context_to_sid_core function in security/selinux/ss/services.c in the Linux kernel before 3.13.4 allows local users to cause a denial of service (system crash) by leveraging the CAP_MAC_ADMIN capability to set a zero-length security context. | https://nvd.nist.gov/vuln/detail/CVE-2014-1874 |
39,355 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static long __media_device_enum_links(struct media_device *mdev,
struct media_links_enum *links)
{
struct media_entity *entity;
entity = find_entity(mdev, links->entity);
if (entity == NULL)
return -EINVAL;
if (links->pads) {
unsigned int p;
for (p = 0; p < entity->num_pads; p++) {
struct medi... | 191,084,336,519,651,900,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,356 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static struct media_entity *find_entity(struct media_device *mdev, u32 id)
{
struct media_entity *entity;
int next = id & MEDIA_ENT_ID_FLAG_NEXT;
id &= ~MEDIA_ENT_ID_FLAG_NEXT;
spin_lock(&mdev->lock);
media_device_for_each_entity(entity, mdev) {
if ((entity->id == id && !next) ||
(entity->id > id && nex... | 260,079,633,221,191,500,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,357 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static int media_device_close(struct file *filp)
{
return 0;
}
| 61,496,663,595,008,785,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,358 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static long media_device_compat_ioctl(struct file *filp, unsigned int cmd,
unsigned long arg)
{
struct media_devnode *devnode = media_devnode_data(filp);
struct media_device *dev = to_media_device(devnode);
long ret;
switch (cmd) {
case MEDIA_IOC_DEVICE_INFO:
case MEDIA_IOC_ENUM_ENTITIES:
case MEDIA_I... | 174,544,590,219,496,230,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,359 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static long media_device_enum_links(struct media_device *mdev,
struct media_links_enum __user *ulinks)
{
struct media_links_enum links;
int rval;
if (copy_from_user(&links, ulinks, sizeof(links)))
return -EFAULT;
rval = __media_device_enum_links(mdev, &links);
if (rval < 0)
return rval;
if (copy_to... | 85,557,494,346,919,940,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,360 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static int media_device_get_info(struct media_device *dev,
struct media_device_info __user *__info)
{
struct media_device_info info;
memset(&info, 0, sizeof(info));
strlcpy(info.driver, dev->dev->driver->name, sizeof(info.driver));
strlcpy(info.model, dev->model, sizeof(info.model));
strlcpy(info.serial, de... | 92,979,142,705,543,360,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,361 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static long media_device_ioctl(struct file *filp, unsigned int cmd,
unsigned long arg)
{
struct media_devnode *devnode = media_devnode_data(filp);
struct media_device *dev = to_media_device(devnode);
long ret;
switch (cmd) {
case MEDIA_IOC_DEVICE_INFO:
ret = media_device_get_info(dev,
(struct medi... | 139,363,330,149,912,880,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,362 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static void media_device_kpad_to_upad(const struct media_pad *kpad,
struct media_pad_desc *upad)
{
upad->entity = kpad->entity->id;
upad->index = kpad->index;
upad->flags = kpad->flags;
}
| 255,119,242,149,803,760,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,363 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static int media_device_open(struct file *filp)
{
return 0;
}
| 275,200,293,834,391,000,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,364 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | int __must_check media_device_register(struct media_device *mdev)
{
int ret;
if (WARN_ON(mdev->dev == NULL || mdev->model[0] == 0))
return -EINVAL;
mdev->entity_id = 1;
INIT_LIST_HEAD(&mdev->entities);
spin_lock_init(&mdev->lock);
mutex_init(&mdev->graph_mutex);
/* Register the device node. */
mdev->devnod... | 227,347,978,418,915,200,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,365 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | int __must_check media_device_register_entity(struct media_device *mdev,
struct media_entity *entity)
{
/* Warn if we apparently re-register an entity */
WARN_ON(entity->parent != NULL);
entity->parent = mdev;
spin_lock(&mdev->lock);
if (entity->id == 0)
entity->id = mdev->entity_id++;
else
mdev->... | 255,967,804,617,915,140,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,366 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static void media_device_release(struct media_devnode *mdev)
{
}
| 311,973,232,788,652,400,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,367 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static long media_device_setup_link(struct media_device *mdev,
struct media_link_desc __user *_ulink)
{
struct media_link *link = NULL;
struct media_link_desc ulink;
struct media_entity *source;
struct media_entity *sink;
int ret;
if (copy_from_user(&ulink, _ulink, sizeof(ulink)))
return -EFAULT;
/* ... | 290,562,783,704,487,670,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,368 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | void media_device_unregister(struct media_device *mdev)
{
struct media_entity *entity;
struct media_entity *next;
list_for_each_entry_safe(entity, next, &mdev->entities, list)
media_device_unregister_entity(entity);
device_remove_file(&mdev->devnode.dev, &dev_attr_model);
media_devnode_unregister(&mdev->devnod... | 2,426,172,555,877,948,300,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,369 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | void media_device_unregister_entity(struct media_entity *entity)
{
struct media_device *mdev = entity->parent;
if (mdev == NULL)
return;
spin_lock(&mdev->lock);
list_del(&entity->list);
spin_unlock(&mdev->lock);
entity->parent = NULL;
}
| 306,142,883,732,013,800,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,370 | linux | e6a623460e5fc960ac3ee9f946d3106233fd28d8 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/e6a623460e5fc960ac3ee9f946d3106233fd28d8 | [media] media-device: fix infoleak in ioctl media_enum_entities()
This fixes CVE-2014-1739.
Signed-off-by: Salva Peiró <speiro@ai2.upv.es>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: stable@vger.kernel.org
Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> | 0 | static ssize_t show_model(struct device *cd,
struct device_attribute *attr, char *buf)
{
struct media_device *mdev = to_media_device(to_media_devnode(cd));
return sprintf(buf, "%.*s\n", (int)sizeof(mdev->model), mdev->model);
}
| 128,243,251,943,082,630,000,000,000,000,000,000,000 | media-device.c | 161,668,849,815,765,700,000,000,000,000,000,000,000 | [
"CWE-200"
] | CVE-2014-1739 | The media_device_enum_entities function in drivers/media/media-device.c in the Linux kernel before 3.14.6 does not initialize a certain data structure, which allows local users to obtain sensitive information from kernel memory by leveraging /dev/media0 read access for a MEDIA_IOC_ENUM_ENTITIES ioctl call. | https://nvd.nist.gov/vuln/detail/CVE-2014-1739 |
39,371 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int __floppy_read_block_0(struct block_device *bdev, int drive)
{
struct bio bio;
struct bio_vec bio_vec;
struct page *page;
struct rb0_cbdata cbdata;
size_t size;
page = alloc_page(GFP_NOIO);
if (!page) {
process_fd_request();
return -ENOMEM;
}
size = bdev->bd_block_size;
if (!size)
size = 102... | 36,044,777,856,900,520,000,000,000,000,000,000,000 | floppy.c | 124,756,562,287,441,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,372 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void __reschedule_timeout(int drive, const char *message)
{
unsigned long delay;
if (drive == current_reqD)
drive = current_drive;
if (drive < 0 || drive >= N_DRIVE) {
delay = 20UL * HZ;
drive = 0;
} else
delay = UDP->timeout;
mod_delayed_work(floppy_wq, &fd_timeout, delay);
if (UDP->flags & FD_... | 189,239,387,991,744,840,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,373 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void bad_flp_intr(void)
{
int err_count;
if (probing) {
DRS->probed_format++;
if (!next_valid_format())
return;
}
err_count = ++(*errors);
INFBOUND(DRWE->badness, err_count);
if (err_count > DP->max_errors.abort)
cont->done(0);
if (err_count > DP->max_errors.reset)
FDCS->reset = 1;
else if (e... | 226,324,680,421,495,000,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,374 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int buffer_chain_size(void)
{
struct bio_vec bv;
int size;
struct req_iterator iter;
char *base;
base = bio_data(current_req->bio);
size = 0;
rq_for_each_segment(bv, current_req, iter) {
if (page_address(bv.bv_page) + bv.bv_offset != base + size)
break;
size += bv.bv_len;
}
return size >> 9;
... | 92,181,927,404,895,100,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,375 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void cancel_activity(void)
{
do_floppy = NULL;
cancel_delayed_work_sync(&fd_timer);
cancel_work_sync(&floppy_work);
}
| 29,228,754,842,334,214,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,376 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void check_wp(void)
{
if (test_bit(FD_VERIFY_BIT, &DRS->flags)) {
/* check write protection */
output_byte(FD_GETSTATUS);
output_byte(UNIT(current_drive));
if (result() != 1) {
FDCS->reset = 1;
return;
}
clear_bit(FD_VERIFY_BIT, &DRS->flags);
clear_bit(FD_NEED_TWADDLE_BIT, &DRS->flags);
... | 102,262,043,095,734,710,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,377 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void __init config_types(void)
{
bool has_drive = false;
int drive;
/* read drive info out of physical CMOS */
drive = 0;
if (!UDP->cmos)
UDP->cmos = FLOPPY0_TYPE;
drive = 1;
if (!UDP->cmos && FLOPPY1_TYPE)
UDP->cmos = FLOPPY1_TYPE;
/* FIXME: additional physical CMOS drive detection should go here ... | 80,384,341,888,734,900,000,000,000,000,000,000,000 | floppy.c | 124,756,562,287,441,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,378 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void copy_buffer(int ssize, int max_sector, int max_sector_2)
{
int remaining; /* number of transferred 512-byte sectors */
struct bio_vec bv;
char *buffer;
char *dma_buffer;
int size;
struct req_iterator iter;
max_sector = transfer_size(ssize,
min(max_sector, max_sector_2),
blk_rq_sectors... | 326,159,223,474,172,070,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,379 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void __init daring(int *ints, int param, int param2)
{
int i;
for (i = 0; i < ARRAY_SIZE(default_drive_params); i++) {
if (param) {
default_drive_params[i].params.select_delay = 0;
default_drive_params[i].params.flags |=
FD_SILENT_DCL_CLEAR;
} else {
default_drive_params[i].params.select_d... | 147,963,419,646,120,760,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,380 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static inline void debugt(const char *func, const char *msg)
{
if (DP->flags & DEBUGT)
pr_info("%s:%s dtime=%lu\n", func, msg, jiffies - debugtimer);
}
| 41,453,786,319,440,545,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,381 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static inline void debugt(const char *func, const char *msg) { }
| 41,743,399,298,923,500,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,382 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int disk_change(int drive)
{
int fdc = FDC(drive);
if (time_before(jiffies, UDRS->select_date + UDP->select_delay))
DPRINT("WARNING disk change called early\n");
if (!(FDCS->dor & (0x10 << UNIT(drive))) ||
(FDCS->dor & 3) != UNIT(drive) || fdc != FDC(drive)) {
DPRINT("probing disk change on unselect... | 291,721,903,903,152,570,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,383 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void do_fd_request(struct request_queue *q)
{
if (WARN(max_buffer_sectors == 0,
"VFS: %s called on non-open device\n", __func__))
return;
if (WARN(atomic_read(&usage_count) == 0,
"warning: usage count=0, current_req=%p sect=%ld type=%x flags=%llx\n",
current_req, (long)blk_rq_pos(current_req), curr... | 176,502,145,125,162,930,000,000,000,000,000,000,000 | floppy.c | 124,756,562,287,441,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,384 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int __init do_floppy_init(void)
{
int i, unit, drive, err;
set_debugt();
interruptjiffies = resultjiffies = jiffies;
#if defined(CONFIG_PPC)
if (check_legacy_ioport(FDC1))
return -ENODEV;
#endif
raw_cmd = NULL;
floppy_wq = alloc_ordered_workqueue("floppy", 0);
if (!floppy_wq)
return -ENOMEM;
for... | 158,489,175,795,031,480,000,000,000,000,000,000,000 | floppy.c | 124,756,562,287,441,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,385 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int do_format(int drive, struct format_descr *tmp_format_req)
{
int ret;
if (lock_fdc(drive, true))
return -EINTR;
set_floppy(drive);
if (!_floppy ||
_floppy->track > DP->tracks ||
tmp_format_req->track >= _floppy->track ||
tmp_format_req->head >= _floppy->head ||
(_floppy->sect << 2)... | 118,001,784,430,832,940,000,000,000,000,000,000,000 | floppy.c | 124,756,562,287,441,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,386 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void do_wakeup(void)
{
reschedule_timeout(MAXTIMEOUT, "do wakeup");
cont = NULL;
command_status += 2;
wake_up(&command_done);
}
| 29,158,195,589,156,260,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,387 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static const char *drive_name(int type, int drive)
{
struct floppy_struct *floppy;
if (type)
floppy = floppy_type + type;
else {
if (UDP->native_format)
floppy = floppy_type + UDP->native_format;
else
return "(null)";
}
if (floppy->name)
return floppy->name;
else
return "(null)";
}
| 98,596,539,688,722,620,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,388 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void empty(void)
{
}
| 71,478,771,208,925,660,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,389 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static inline void fallback_on_nodma_alloc(char **addr, size_t l)
{
#ifdef FLOPPY_CAN_FALLBACK_ON_NODMA
if (*addr)
return; /* we have the memory */
if (can_use_virtual_dma != 2)
return; /* no fallback allowed */
pr_info("DMA memory shortage. Temporarily falling back on virtual DMA\n");
*addr = (char *)nodma_m... | 269,217,242,331,005,170,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,390 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static inline int fd_copyin(void __user *param, void *address,
unsigned long size)
{
return copy_from_user(address, param, size) ? -EFAULT : 0;
}
| 70,405,196,657,900,960,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,391 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static inline int fd_copyout(void __user *param, const void *address,
unsigned long size)
{
return copy_to_user(param, address, size) ? -EFAULT : 0;
}
| 148,065,949,675,332,850,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,392 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static inline int fd_eject(int drive)
{
return -EINVAL;
}
| 107,362,417,276,833,040,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,393 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int fd_getgeo(struct block_device *bdev, struct hd_geometry *geo)
{
int drive = (long)bdev->bd_disk->private_data;
int type = ITYPE(drive_state[drive].fd_device);
struct floppy_struct *g;
int ret;
ret = get_floppy_geometry(drive, type, &g);
if (ret)
return ret;
geo->heads = g->head;
geo->sectors = g-... | 253,366,646,066,139,280,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,394 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int fd_ioctl(struct block_device *bdev, fmode_t mode,
unsigned int cmd, unsigned long param)
{
int ret;
mutex_lock(&floppy_mutex);
ret = fd_locked_ioctl(bdev, mode, cmd, param);
mutex_unlock(&floppy_mutex);
return ret;
}
| 147,947,643,682,862,200,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,395 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int fd_locked_ioctl(struct block_device *bdev, fmode_t mode, unsigned int cmd,
unsigned long param)
{
int drive = (long)bdev->bd_disk->private_data;
int type = ITYPE(UDRS->fd_device);
int i;
int ret;
int size;
union inparam {
struct floppy_struct g; /* geometry */
struct format_descr f;
struct ... | 80,923,048,851,793,450,000,000,000,000,000,000,000 | floppy.c | 124,756,562,287,441,240,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,396 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void fd_watchdog(void)
{
debug_dcl(DP->flags, "calling disk change from watchdog\n");
if (disk_change(current_drive)) {
DPRINT("disk removed during i/o\n");
cancel_activity();
cont->done(0);
reset_fdc();
} else {
cancel_delayed_work(&fd_timer);
fd_timer_fn = fd_watchdog;
queue_delayed_work(flop... | 255,929,723,962,635,500,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,397 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int fdc_configure(void)
{
/* Turn on FIFO */
output_byte(FD_CONFIGURE);
if (need_more_output() != MORE_OUTPUT)
return 0;
output_byte(0);
output_byte(0x10 | (no_fifo & 0x20) | (fifo_depth & 0xf));
output_byte(0); /* pre-compensation from track
0 upwards */
return 1;
}
| 230,098,634,720,866,430,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,398 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static int fdc_dtr(void)
{
/* If data rate not already set to desired value, set it. */
if ((raw_cmd->rate & 3) == FDCS->dtr)
return 0;
/* Set dtr */
fd_outb(raw_cmd->rate & 3, FD_DCR);
/* TODO: some FDC/drive combinations (C&T 82C711 with TEAC 1.2MB)
* need a stabilization period of several milliseconds to ... | 196,690,114,820,061,870,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,399 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static void fdc_specify(void)
{
unsigned char spec1;
unsigned char spec2;
unsigned long srt;
unsigned long hlt;
unsigned long hut;
unsigned long dtr = NOMINAL_DTR;
unsigned long scale_dtr = NOMINAL_DTR;
int hlt_max_code = 0x7f;
int hut_max_code = 0xf;
if (FDCS->need_configure && FDCS->version >= FDC_82072A) ... | 241,914,260,171,551,400,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,400 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static __init void floppy_async_init(void *data, async_cookie_t cookie)
{
do_floppy_init();
}
| 61,920,454,596,130,540,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
39,401 | linux | 2145e15e0557a01b9195d1c7199a1b92cb9be81f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/2145e15e0557a01b9195d1c7199a1b92cb9be81f | floppy: don't write kernel-only members to FDRAWCMD ioctl output
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the pointer to the allocated
DMA space.
Signed-off-by: Matthew Daley <mattd@bugfuzz.com>
Signed-off-by: Linus Torvalds <torvalds@linux-found... | 0 | static bool floppy_available(int drive)
{
if (!(allowed_drive_mask & (1 << drive)))
return false;
if (fdc_state[FDC(drive)].version == FDC_NONE)
return false;
return true;
}
| 193,285,733,534,732,540,000,000,000,000,000,000,000 | floppy.c | 56,207,149,155,076,080,000,000,000,000,000,000,000 | [
"CWE-264"
] | CVE-2014-1738 | The raw_cmd_copyout function in drivers/block/floppy.c in the Linux kernel through 3.14.3 does not properly restrict access to certain pointers during processing of an FDRAWCMD ioctl call, which allows local users to obtain sensitive information from kernel heap memory by leveraging write access to a /dev/fd device. | https://nvd.nist.gov/vuln/detail/CVE-2014-1738 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.